Date: Wed, 07 Jan 2009 10:33:09 -0800 From: Tim Kientzle <kientzle@freebsd.org> To: Kris Kennaway <kris@freebsd.org> Cc: freebsd-hackers@freebsd.org, Christian Weisgerber <naddy@mips.inka.de> Subject: Re: lzo2 shows insane speed gap Message-ID: <4964F565.2080201@freebsd.org> In-Reply-To: <4961294D.8080200@FreeBSD.org> 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> <4961294D.8080200@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Kris Kennaway wrote: > 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. >> ... >> >> But still. Two orders of magnitude? That is a pathological case. > > Probably it means that lzo2 is doing pathological numbers of mallocs. Rather, the lzo2 test suite. Test suites do tend to hammer malloc() pretty hard. I see similar variations for the libarchive test suite with malloc debugging. Tim
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4964F565.2080201>