Date: Wed, 13 Mar 2002 22:42:08 -0800 From: David Greenman <dg@root.com> To: Kris Kennaway <kris@obsecurity.org> Cc: John Indra <maverick@office.naver.co.id>, freebsd-current@FreeBSD.ORG, Alfred Perlstein <bright@mu.org> Subject: Re: malloc() and the stock Perl in -CURRENT (and -STABLE) Message-ID: <20020313224208.K27616@nexus.root.com> In-Reply-To: <20020313223647.A20636@xor.obsecurity.org>; from kris@obsecurity.org on Wed, Mar 13, 2002 at 10:36:47PM -0800 References: <20020314104525.B8244@office.naver.co.id> <20020314052810.GH74829@elvis.mu.org> <20020314124729.E8244@office.naver.co.id> <20020313223647.A20636@xor.obsecurity.org>
next in thread | previous in thread | raw e-mail | index | archive | help
>On Thu, Mar 14, 2002 at 12:47:29PM +0700, John Indra wrote: > >> And to clarify things... I don't know what's wrong with malloc() in -CURRENT >> and -STABLE (and I don't even know whether it's even "wrong"). All I want is >> to let the Perl maintainer in -CURRENT and -STABLE to compile the stock Perl >> with its own malloc library, thus Perl in FreeBSD doesn't suffer from this >> kind of slowness. > >phkmalloc is generally pretty efficient..how do you know that >switching to the perl internal malloc to optimize this particular >usage pattern won't severely pessimize others? If you read the bug report, you'll see that using perl's malloc results in the program running more than 10 times faster. -DG David Greenman Co-founder, The FreeBSD Project - http://www.freebsd.org President, TeraSolutions, Inc. - http://www.terasolutions.com President, Download Technologies, Inc. - http://www.downloadtech.com Pave the road of life with opportunities. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020313224208.K27616>