memory
snmalloc
| memory | snmalloc | |
|---|---|---|
| 1 | 8 | |
| 1,490 | 1,560 | |
| - | 0.9% | |
| 2.9 | 7.2 | |
| 2 months ago | 7 days ago | |
| C++ | C++ | |
| zlib License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
memory
-
You all need to stop blindly recommending 32 GB of RAM
In general you'll get a lot of interesting information if you search for "cache locality", "data locality", "custom memory allocation" and read stuff that people have written on github (for example https://github.com/foonathan/memory).
snmalloc
-
Snmalloc: A Message Passing Allocator
https://github.com/microsoft/snmalloc#snmalloc mentions two biggest motivations as:
> Allocations on one thread are freed by a different thread
I can imagine one use-case for this: a task that is scheduled from and executed by a work-stealing thread-pool can allocate memory in one thread but by design there's no guarantee that the memory will be necessarily freed from that exact thread. Would that be a good use-case for snmalloc?
> Deallocations occur in large batches
This sounds much like a bump allocator use-case but which can do this exact thing by calling a single munmap(addr, len) and unmap multiple allocations all at once.
-
Is the JVM a upside or downside to Scala?
Yes, it's very efficient and that's not where the main problem lies. However, small allocations with modern C heap allocators like mimalloc or snmalloc has gotten extremely efficient as well. Would be interesting to see a benchmark comparison with Java's G1 and ZGC.
- Snmalloc 0.6 released, major redesign with security hardening
- Snmalloc: High-performance message passing based allocator
-
Maintenance status (jemallocator)
Did you ever benchmark against https://github.com/microsoft/snmalloc ?
What are some alternatives?
o1heap - Constant-complexity deterministic memory allocator (heap) for hard real-time high-integrity embedded systems. There is very little activity because the project is finished and does not require further changes.
mimalloc - mimalloc is a compact general purpose allocator with excellent performance.
Mesh - A memory allocator that automatically reduces the memory footprint of C/C++ applications.
jemallocator - Rust allocator using jemalloc as a backend
memory-allocators - Custom memory allocators in C++ to improve the performance of dynamic memory allocation
mimalloc_rust - A Rust wrapper over Microsoft's MiMalloc memory allocator
lfjson - A memory-optimized and data-oriented JSON library written in C++
mlaas - Simply the best way to instill a sense of urgency within your engineering team.
rpmalloc - Public domain cross platform lock free thread caching 16-byte aligned memory allocator implemented in C
jemallocator - Rust allocator using jemalloc as a backend