Date: Wed, 13 Mar 2002 22:36:47 -0800 From: Kris Kennaway <kris@obsecurity.org> To: John Indra <maverick@office.naver.co.id> Cc: freebsd-current@FreeBSD.ORG, Alfred Perlstein <bright@mu.org> Subject: Re: malloc() and the stock Perl in -CURRENT (and -STABLE) Message-ID: <20020313223647.A20636@xor.obsecurity.org> In-Reply-To: <20020314124729.E8244@office.naver.co.id>; from maverick@office.naver.co.id on Thu, Mar 14, 2002 at 12:47:29PM %2B0700 References: <20020314104525.B8244@office.naver.co.id> <20020314052810.GH74829@elvis.mu.org> <20020314124729.E8244@office.naver.co.id>
next in thread | previous in thread | raw e-mail | index | archive | help
--rwEMma7ioTxnRzrJ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline 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? Kris --rwEMma7ioTxnRzrJ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE8kET/Wry0BWjoQKURAgIYAKCTwtsMlseJ0FL57eDCnq8N8l7jYgCg6XW2 /OLpDPABlXXnpcbV28nwlVc= =3qcR -----END PGP SIGNATURE----- --rwEMma7ioTxnRzrJ-- 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?20020313223647.A20636>