All Projects → emeryberger → Heap Layers

emeryberger / Heap Layers

Licence: apache-2.0
Heap Layers: An Extensible Memory Allocation Infrastructure

Projects that are alternatives of or similar to Heap Layers

Sralloc
Memory allocators
Stars: ✭ 25 (-90.38%)
Mutual labels:  memory-management, memory-allocation
smalloc
SMalloc -- a *static* memory allocator.
Stars: ✭ 22 (-91.54%)
Mutual labels:  memory-management, memory-allocation
Scalene
Scalene: a high-performance, high-precision CPU, GPU, and memory profiler for Python
Stars: ✭ 4,819 (+1753.46%)
Mutual labels:  memory-management, memory-allocation
Heapinspector For Ios
Find memory issues & leaks in your iOS app without instruments
Stars: ✭ 1,819 (+599.62%)
Mutual labels:  memory-management, memory-allocation
MemoryAllocator.KanameShiki
Fast multi-threaded memory allocator
Stars: ✭ 73 (-71.92%)
Mutual labels:  memory-management, memory-allocation
buddy alloc
A single header buddy memory allocator for C
Stars: ✭ 46 (-82.31%)
Mutual labels:  memory-management, memory-allocation
Rmm
RAPIDS Memory Manager
Stars: ✭ 154 (-40.77%)
Mutual labels:  memory-management, memory-allocation
GC
A lightweight conservative garbage collector for C/C++
Stars: ✭ 108 (-58.46%)
Mutual labels:  memory-management, memory-allocation
on-the-fly-gc
Concurrent mark-sweep garbage collector for accurate garbage collection of language runtimes in C++ 1x.
Stars: ✭ 25 (-90.38%)
Mutual labels:  memory-management
Unity-delayed-asset
**DEPRECATED** Plugin for Unity that allows to assign assets in the inspector while preventing Unity from automatically loading the assets in memory when a scene is loaded
Stars: ✭ 19 (-92.69%)
Mutual labels:  memory-management
kernel memory management
总结整理linux内核的内存管理的资料,包含论文,文章,视频,以及应用程序的内存泄露,内存池相关
Stars: ✭ 521 (+100.38%)
Mutual labels:  memory-management
Weakify
Provides a way use a method on a class as a closure value that would be referenced by some other component without causing memory leaks.
Stars: ✭ 65 (-75%)
Mutual labels:  memory-management
scaraOS
A 32bit multiboot OS kernel for IA32 (PC/AT) systems.
Stars: ✭ 31 (-88.08%)
Mutual labels:  memory-management
taskbar-monitor
monitoring tool with graphs (CPU, memory, disk and network) for Windows taskbar.
Stars: ✭ 121 (-53.46%)
Mutual labels:  memory-management
rs-process-memory
A rust library that allows you to read/write into the memory of other processes
Stars: ✭ 63 (-75.77%)
Mutual labels:  memory-management
memsec
Rust implementation `libsodium/utils`.
Stars: ✭ 39 (-85%)
Mutual labels:  memory-management
Cone
Cone Programming Language
Stars: ✭ 257 (-1.15%)
Mutual labels:  memory-management
redis-key-dashboard
This tool allows you to do a small analysis of the amount of keys and memory you use in Redis. It allows you to see overlooked keys and notice overuse.
Stars: ✭ 42 (-83.85%)
Mutual labels:  memory-management
gctoolkit
Tool for parsing GC logs
Stars: ✭ 1,127 (+333.46%)
Mutual labels:  memory-management
Memory-Management-and-Advanced-Debugging-techniques
Tutorial:Memory Management and Advanced Debugging techniques
Stars: ✭ 25 (-90.38%)
Mutual labels:  memory-management

Heap Layers: An Extensible Memory Allocation Infrastructure

Copyright (C) 2000 - 2021 by Emery Berger

Heap Layers is distributed under the terms of the Apache 2.0 license.

Introduction

Heap Layers provides a flexible infrastructure for composing high-performance memory allocators out of C++ layers. Heap Layers makes it easy to write high-quality custom and general-purpose memory allocators. Heap Layers has been used successfully to build a number of high-performance allocators, including Hoard and DieHard.

Using Heap Layers

For an introduction to Heap Layers, read the article Policy-Based Memory Allocation, by Andrei Alexandrescu and Emery Berger. It's a good overview. See also "Memory Allocation: Either Love It or Hate It (or just think it’s okay)", a talk by Andrei.

Heap Layers contains a number of ready-made heap components that can be plugged together with minimal effort, and the result is often faster than hand-built allocators. The PLDI 2001 paper Composing High-Performance Memory Allocators has plenty of examples.

Performance

Heap Layers can substantially outperform its only real competitor, the Vmalloc package from AT&T. The OOPSLA 2002 paper Reconsidering Custom Memory Allocation paper has more details.

Not only is Heap Layers much higher level and simpler to use, but its use of templates also improves performance. Heap Layers both eliminates the function call overhead imposed by Vmalloc layers and yields higher quality code by exposing more optimization opportunities.

Citation

To reference Heap Layers in an academic paper, please cite as follows:

@inproceedings{DBLP:conf/pldi/BergerZM01,
  author    = {Emery D. Berger and
               Benjamin G. Zorn and
               Kathryn S. McKinley},
  title     = {Composing High-Performance Memory Allocators},
  booktitle = {Proceedings of the 2001 {ACM} {SIGPLAN} Conference on Programming
               Language Design and Implementation (PLDI), Snowbird, Utah, USA, June
               20-22, 2001},
  pages     = {114--124},
  year      = {2001},
  crossref  = {DBLP:conf/pldi/2001},
  url       = {https://doi.org/10.1145/378795.378821},
  doi       = {10.1145/378795.378821},
  timestamp = {Wed, 14 Nov 2018 10:54:59 +0100},
  biburl    = {https://dblp.org/rec/bib/conf/pldi/BergerZM01},
  bibsource = {dblp computer science bibliography, https://dblp.org}
}

@proceedings{DBLP:conf/pldi/2001,
  editor    = {Michael Burke and
               Mary Lou Soffa},
  title     = {Proceedings of the 2001 {ACM} {SIGPLAN} Conference on Programming
               Language Design and Implementation (PLDI), Snowbird, Utah, USA, June
               20-22, 2001},
  publisher = {{ACM}},
  year      = {2001},
  url       = {http://dl.acm.org/citation.cfm?id=378795},
  isbn      = {1-58113-414-2},
  timestamp = {Mon, 21 May 2012 16:19:53 +0200},
  biburl    = {https://dblp.org/rec/bib/conf/pldi/2001},
  bibsource = {dblp computer science bibliography, https://dblp.org}
}
Note that the project description data, including the texts, logos, images, and/or trademarks, for each open source project belongs to its rightful owner. If you wish to add or remove any projects, please contact us at [email protected].