From owner-freebsd-hackers@FreeBSD.ORG Wed Jan 7 18:33:14 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 991EE1065674 for ; Wed, 7 Jan 2009 18:33:14 +0000 (UTC) (envelope-from kientzle@freebsd.org) Received: from kientzle.com (kientzle.com [66.166.149.50]) by mx1.freebsd.org (Postfix) with ESMTP id 6E2EA8FC14 for ; Wed, 7 Jan 2009 18:33:14 +0000 (UTC) (envelope-from kientzle@freebsd.org) Received: from [10.123.2.23] (p53.kientzle.com [66.166.149.53]) by kientzle.com (8.12.9/8.12.9) with ESMTP id n07IXBtv045338; Wed, 7 Jan 2009 10:33:11 -0800 (PST) (envelope-from kientzle@freebsd.org) Message-ID: <4964F565.2080201@freebsd.org> Date: Wed, 07 Jan 2009 10:33:09 -0800 From: Tim Kientzle User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20060422 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Kris Kennaway References: <20081230004747.GA55542@lorvorc.mips.inka.de> <20081230020524.2563a6ac@gluon> <4961294D.8080200@FreeBSD.org> In-Reply-To: <4961294D.8080200@FreeBSD.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org, Christian Weisgerber Subject: Re: lzo2 shows insane speed gap X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Jan 2009 18:33:15 -0000 Kris Kennaway wrote: > Christian Weisgerber wrote: >> Bruce Cran 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