Date: Mon, 14 May 2007 13:30:26 +0100 (BST) From: Robert Watson <rwatson@FreeBSD.org> To: Ivan Voras <ivoras@fer.hr> Cc: Alfred Perlstein <alfred@freebsd.org>, freebsd-arch@freebsd.org Subject: Re: HEADS DOWN Message-ID: <20070514132901.X24765@fledge.watson.org> In-Reply-To: <46478C9A.9050807@fer.hr> References: <20070512153532.GQ21795@elvis.mu.org> <63984.1178992555@critter.freebsd.dk> <f25m78$ik$2@sea.gmane.org> <20070513215442.GZ21795@elvis.mu.org> <46478C9A.9050807@fer.hr>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 14 May 2007, Ivan Voras wrote: > (This being said, since I'm not going to create a malloc implementation any > time soon, it of course depends on the particular author what will or will > not be supported :) ). > >> And since our allocator is vastly superior > > phkmalloc isn't any more and it remains to be seen for jemalloc :) Actually, competitive MySQL benchmarking against Linux seems to illustrate that jemalloc is dramatically more scalable than the native glibc malloc, and comparable with the google malloc. I have to admit, however, that I do wish we'd retained an easy switch to let us go back and forth between phkmalloc and jemalloc for comparison purposes. Robert N M Watson Computer Laboratory University of Cambridge
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070514132901.X24765>