I tried google allocator under Linux and NS just crashed, so i did not
bother to investigate.
Is memory contention that big so new memory allocator is needed, i never
looked into that and do not have
clear picture why this zippy appeared in the first place. What kind of
numbers we are talking about comparing
zippy and regular mallocs?
Zoran Vasiljevic wrote:
Am 06.04.2005 um 20:39 schrieb Vlad Seryakov:
I used valgrind and it complained about huge memory leaks somewhere in
the thread allocation, nothing in particular but it pointed on
Ns_CsInit function when used master lock. I could not figure out there
anything, it is just simple plain ns_calloc but still, when
zippy disabled it is running fine.
Do you primarily use Linux? In that case the ptmalloc should be already
there in glibc
and this whole junk can safely be skipped.
Our problem is that we need it for Solaris and Mac OSX and Windows and
Linux.
Hence I must try the standalone ptmalloc unless I get the Tcl built-in
allocator
working sane. And, I yet have to see what is the situation looking like
on the Win...
But as the Jim Davidson writes:
"Going forward, there are likley newer options such as the google
allocator which is similar to
zippy for small blocks but appears to be smarter for large blocks
and/or garbage collection."
Bah... this thing even does not compile on Darwin...
Zoran
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
naviserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/naviserver-devel
--
Vlad Seryakov
571 262-8608 office
[EMAIL PROTECTED]
http://www.crystalballinc.com/vlad/
