Date: Thu, 05 Apr 2001 18:39:23 +0300 From: Maxim Sobolev <sobomax@FreeBSD.org> To: Poul-Henning Kamp <phk@critter.freebsd.dk> Cc: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: ports/devel Makefile ports/devel/dlmalloc Makefile distinfo pkg-comment pkg-descr pkg-message pkg-plist ports/devel/dlmalloc/files Makefile README.FreeBSD Message-ID: <3ACC91AB.2A183123@FreeBSD.org> References: <22562.986484362@critter>
next in thread | previous in thread | raw e-mail | index | archive | help
Poul-Henning Kamp wrote: > In message <200104051517.f35FHXb44816@freefall.freebsd.org>, Maxim Sobolev writes: > >sobomax 2001/04/05 08:17:33 PDT > > > > Modified files: > > devel Makefile > > Added files: > > devel/dlmalloc Makefile distinfo pkg-comment pkg-descr > > pkg-message pkg-plist > > devel/dlmalloc/files Makefile README.FreeBSD > > Log: > > Add dlmalloc 2.7.0, a very efficient malloc/free/realloc implementation. > > > > According to my tests it is *amazingly* efficient - it gave me about 10% > > memory saving (SIZE in the top(1)) for the large processes like X and jre > > without any measureable performance saturation. > > > > Moreover, due to not very clear for me reasons Python benchmark (pybench) > > is about 60% (!!!) faster with this allocator comparing to the libc one. > > Obviously we should investigate this further and if there is no error > > then tune either Python or our own malloc. > > Did you measure this with the right malloc flags for the libc version ? > > Remember that -current runs with malloc flags "AJ" as default, that is not > fair if it comes to performance comparisons (but it does wonders for finding > bugs :-) I don't use default value: $ ls -l /etc/malloc.conf lrwxr-xr-x 1 root wheel 7 Jul 22 2000 /etc/malloc.conf@ -> HRajuxz -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3ACC91AB.2A183123>