From owner-freebsd-current@FreeBSD.ORG Thu Jul 29 09:37:53 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0A07616A4CF for ; Thu, 29 Jul 2004 09:37:53 +0000 (GMT) Received: from robbins.dropbear.id.au (113.a.004.mel.iprimus.net.au [210.50.36.113]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9C1FC43D5C for ; Thu, 29 Jul 2004 09:37:49 +0000 (GMT) (envelope-from tim@robbins.dropbear.id.au) Received: by robbins.dropbear.id.au (Postfix, from userid 1000) id 947504208; Thu, 29 Jul 2004 19:37:31 +1000 (EST) Date: Thu, 29 Jul 2004 19:37:31 +1000 From: Tim Robbins To: Danny Braniss Message-ID: <20040729093731.GA6025@cat.robbins.dropbear.id.au> References: <20040729092235.5F3B143D66@mx1.FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040729092235.5F3B143D66@mx1.FreeBSD.org> User-Agent: Mutt/1.4.1i cc: freebsd current Subject: Re: malloc in the slow lane X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Jul 2004 09:37:53 -0000 On Thu, Jul 29, 2004 at 12:22:09PM +0300, Danny Braniss wrote: > hi, > just came across a 'anomality'. The kernel is -current, > the same program, compiled under -stable, runs 'fast', while > the compiled under -current, is slowwwwwwwwwwww. > > According to the UPDATING note, this is supposed to be expected, but > can't find a fix. > > some data: > i386-freebsd5.2/memsize: > libm.so.2 => /lib/libm.so.2 (0x48077000) > libc.so.5 => /lib/libc.so.5 (0x48090000) > i386-freebsd4.9/memsize: > libm.so.2 => /lib/libm.so.2 (0x48078000) > libc.so.4 => /usr/lib/compat/libc.so.4 (0x48091000) > > time i386-freebsd5.2/memsize 32 > 0.548u 1.073s 0:01.62 99.3% 25+33211k 0+0io 0pf+0w > time i386-freebsd4.9/memsize 32 > 0.009u 0.062s 0:00.07 85.7% 32+43957k 0+0io 0pf+0w > > any insights? The 'J' malloc(3) debugging flag is enabled by default on -CURRENT, but is not enabled on RELENG_4 or any release branches. Try "ln -sf j /etc/malloc.conf". Tim