#7420: Hoard allocator assumes wrong cache line size
---------------------------------+----------------------------
Reporter: jonas.kirilla | Owner: axeld
Type: bug | Status: new
Priority: normal | Milestone: R1
Component: System/libroot.so | Version: R1/Development
Resolution: | Keywords:
Blocked By: | Blocking:
Has a Patch: 0 | Platform: All
---------------------------------+----------------------------
Comment (by pulkomandy):
malloc alternatives:
* nedmalloc http://www.nedprod.com/programs/portable/nedmalloc/ (Boost
License)
* WebKit bmalloc
https://github.com/WebKit/webkit/tree/f135574084f1393927d7349beccbe8f3af741995/Source/bmalloc/bmalloc
(2-clause BSD) - WebKit is switching from TCMalloc to bmalloc
* tcmalloc http://gperftools.googlecode.com/git/doc/tcmalloc.html (3
clause BSD)
* jemalloc http://www.canonware.com/jemalloc/ (2 clause BSD)
* lockless http://locklessinc.com/benchmarks_allocator.shtml (commercial)
- provides a comparison/benchmark with hoard, nedmalloc, tcmalloc and
jemalloc
Most benchmarks focus on performance, but we should also have a look at
memory overhead and management of low-resource situation (it seems
tcmalloc won't give memory back to the system in some cases for example).
--
Ticket URL: <https://dev.haiku-os.org/ticket/7420#comment:4>
Haiku <https://dev.haiku-os.org>
Haiku - the operating system.
