On 15.12.2006, at 19:59, Vlad Seryakov wrote:
I also tried Hoard, Google tcmalloc, umem and some other rare
mallocs i
could find. Still zippy beats everybody, i ran my speed test not
threadtest. Will try this one.
Important: it is not only raw speed, that is important but also
the memory fragmentation (i.e. lack of it).
In our app we must frequently reboot the server (each couple of
days) otherwise it just bloats. And... we made sure there are
no leaks (have purified all libs that we use)...
I now have some experience with the (zippy) fragmentation and I will
try to make a testbed with this allocator and run it for several
days to get some experience.
Cheers
Zoran
