FreeLists / openbeos / [openbeos] Re: Hoard and other allocators

["Ari Haviv" <arielbhaviv@xxxxxxxxx>]

Someone did an independent benchmark and concluded "Looks like the
nedmalloc guy has the most realistic claims."
http://www.osnews.com/comments/17977
As for firefox, they had a big memory problem to deal with and they
compared fragmentation as you can see in this nice picture gallery:
http://blog.pavlov.net/2007/12/04/vlad-and-analysis-of-dtrace-was-used/


On Mon, Apr 7, 2008 at 4:50 AM, Axel Dörfler <axeld@xxxxxxxxxxxxxxxx> wrote:
>
>
>  Nothing important has changed since then (besides the license), AFAIK,
>  though.
>  Anyway, there is also the allocator of the Google performance tools.
>
>  IMO the hoard allocator serves us nicely for now. Once we have a useful
>  set of benchmarks ported to Haiku, we might want to reevaluate the
>  allocator issue, though.
>  Usually, the allocators I've seen so far are hesitant to compare
>  themselves with real competitors - they usually only benchmark against
>  some old ones.
>
>  Bye,
>    Axel.
>
>
>