previousupnext

1.3 LeapHeap Organisation

When you run an application with LeapHeap, the creation of multiple heaps is forestalled. LeapHeap reserves sufficient memory for one huge heap, utilised by all DLLs and threads.

With LeapHeap, your threads do not need private heaps because the LeapHeap algorithms are inherently threadsafe without critical regions and for trivial overhead. They run lock-free.

LeapHeap segregates heap allocations by size so that (for example) all C++ objects of a given class are stored in the same memory compartment, and to some extent by thread. Thus LeapHeap provides high locality without the complication of dedicated heaps.

LeapHeap returns the memory of a process to its simplest, least fragmented state:



1.3.1 Memory States
1.3.2 The Gigabyte Heap