Date: Sun, 04 Jan 2009 21:25:33 +0000 From: Kris Kennaway <kris@FreeBSD.org> To: Christian Weisgerber <naddy@mips.inka.de> Cc: freebsd-hackers@freebsd.org Subject: Re: lzo2 shows insane speed gap Message-ID: <4961294D.8080200@FreeBSD.org> In-Reply-To: <gjd77i$1h19$1@lorvorc.mips.inka.de> References: <gjbf7c$hbm$1@lorvorc.mips.inka.de> <Pine.GSO.4.64.0812291512490.22968@zeno.ucsd.edu> <20081230004747.GA55542@lorvorc.mips.inka.de> <20081230020524.2563a6ac@gluon> <gjd77i$1h19$1@lorvorc.mips.inka.de>
next in thread | previous in thread | raw e-mail | index | archive | help
Christian Weisgerber wrote: > Bruce Cran <bruce@cran.org.uk> wrote: > >> I'm running 8.0-CURRENT amd64 here on a Turion64 X2 machine. Without >> malloc debugging (malloc.conf -> aj) 'make test' takes 25s; after >> removing malloc.conf thus turning on debugging, it takes over 10 >> minutes. > > Wow! That. Is. It. > > Toggling malloc debugging option J makes the "slow" machines "fast" > and vice versa. > >>> Athlon 64 X2 5200+ 2.6 GHz, FreeBSD 8.0-CURRENT amd64 ~60 min > > 19 seconds. > > I guess that falls under the "obvious" configuration differences > to check, but since it usually doesn't cause a significant slowdown > I completely forgot about it. Embarrassing. > > But still. Two orders of magnitude? That is a pathological case. > Probably it means that lzo2 is doing pathological numbers of mallocs. Kris
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4961294D.8080200>