Hacker News Reader

Full thread

throwaway4891a

See also:

- http://locklessinc.com/benchmarks_allocator.shtml ($, use as a minimum performance target)

- http://www.nedprod.com/programs/portable/nedmalloc/

- http://phk.freebsd.dk/pubs/malloc.pdf [PDF] (phkmalloc)

- https://github.com/gperftools/gperftools (tcmalloc)

- https://github.com/ivmai/bdwgc/blob/master/malloc.c

- https://github.com/jemalloc/jemalloc

- http://gee.cs.oswego.edu/dl/html/malloc.html (dlmalloc)

View on HN

Thank 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.

Aha, I see.. Very nice. Like the following implementation of free() as commonly used in HFT:

void free(void *mem) {}

That's a totally valid solution to some problems :) Having access to a decent allocator protocol lets you do that and more.

Reply on news.ycombinator.com