3 ms·
See also: - http://locklessinc.com/benchmarks_allocator.shtml http://locklessinc.com/benchmarks_allocator.shtml ($, use as a minimum performance target) - htt
by throwaway4891a 10y ago
See also:
- http://locklessinc.com/benchmarks_allocator.shtml http://locklessinc.com/benchmarks_allocator.shtml ($, use as a minimum performance target)
- http://www.nedprod.com/programs/portable/nedmalloc/ http://www.nedprod.com/programs/portable/nedmalloc/
- http://phk.freebsd.dk/pubs/malloc.pdf http://phk.freebsd.dk/pubs/malloc.pdf [PDF] (phkmalloc)
- https://github.com/gperftools/gperftools https://github.com/gperftools/gperftools (tcmalloc)
- https://github.com/ivmai/bdwgc/blob/master/malloc.c https://github.com/ivmai/bdwgc/blob/master/malloc.c
- https://github.com/jemalloc/jemalloc https://github.com/jemalloc/jemalloc
- http://gee.cs.oswego.edu/dl/html/malloc.html http://gee.cs.oswego.edu/dl/html/malloc.html (dlmalloc)
- codr4life 10y agoThank you, but that's not the problem I'm solving. Any one of those could be used to feed any implementation from the challenge. The idea I'm pushing is using local knowledge to customize memory management, instead of trying to find the perfect one-size-fits-all solution.
- mathgenius 10y agoAha, I see.. Very nice. Like the following implementation of free() as commonly used in HFT: void free(void *mem) {}
- codr4life 10y agoThat's a totally valid solution to some problems :) Having access to a decent allocator protocol lets you do that and more.