3 ms·
This example implementation should come with a disclaimer: keeping metadata inside the allocated objects is a bad idea because it pollutes the caches and increa
by lgeek 13y ago
This example implementation should come with a disclaimer: keeping metadata inside the allocated objects is a bad idea because it pollutes the caches and increases fragmentation.
I think the problem of memory allocation becomes much more interesting in the context of multithreaded applications. I really like the streamflow paper[0]. For similar implementations that are more widely used nowadays, see hoard[1], jemalloc[2] and tcmalloc[3].
Edit: it turns out one of the authors of streamflow was posting in this tread: https://news.ycombinator.com/item?id=5722049 https://news.ycombinator.com/item?id=5722049
[0] http://haiocl.googlecode.com/svn-history/r21/trunk/doc/papers/ismm06.pdf http://haiocl.googlecode.com/svn-history/r21/trunk/doc/paper...
[1] http://www.hoard.org/ http://www.hoard.org/
[2] http://people.freebsd.org/~jasone/jemalloc/bsdcan2006/jemalloc.pdf http://people.freebsd.org/~jasone/jemalloc/bsdcan2006/jemall...
[3] http://goog-perftools.sourceforge.net/doc/tcmalloc.html http://goog-perftools.sourceforge.net/doc/tcmalloc.html
- scott_s 13y agoThanks for making my day. I would have emailed that to you, but you don't have any contact information in your profile.