Date: Thu, 14 Apr 2005 17:26:40 +0100 From: "Niall Douglas" <s_sourceforge@nedprod.com> To: freebsd-threads@freebsd.org Subject: Re: thread aware malloc Message-ID: <425EA7D0.20279.12A9E357@localhost> In-Reply-To: <425E4B01.2020104@fer.hr> References: <425E4810.7553.1133DEA0@localhost>
next in thread | previous in thread | raw e-mail | index | archive | help
On 14 Apr 2005 at 12:50, Ivan Voras wrote: > > I finally have a native 64 bit platform which I just bought, I'm > > just waiting on the release of v5.4. I'll post benchmarks here when > > I know, but I'm still expecting an order of magnitude difference. > > For performance reasons, RELENG_5_4 in the current state will be the > same as 5.4-RELEASE[1] - no way re@ would allow serious commits to it > :) If you're planning doing benchmarks on real hardware (not vmware), > which would be most interesting, you might as well start doing it now > (or do the linux part now, do preliminary 5.4, and update to > 5.4-release when it's ready, maybe repeat benchmarks) My university does not permit use of CVS or CVSup (firewalled), so I'll be waiting for the release. > Also, to avoid flames, you might want to run the results through > ministat (/usr/src/tools/tools/ministat) :) Useful. > [1] : You might need to exclude debugging facilities from kernel - > witness & invariants mostly, and do 'ln -fs jrz /etc/malloc.conf' Noted. Cheers, Niall
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?425EA7D0.20279.12A9E357>