Date: Thu, 29 Jul 2004 19:37:31 +1000 From: Tim Robbins <tjr@freebsd.org> To: Danny Braniss <danny@cs.huji.ac.il> Cc: freebsd current <current@freebsd.org> Subject: Re: malloc in the slow lane Message-ID: <20040729093731.GA6025@cat.robbins.dropbear.id.au> In-Reply-To: <20040729092235.5F3B143D66@mx1.FreeBSD.org> References: <20040729092235.5F3B143D66@mx1.FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040729093731.GA6025>