From owner-freebsd-current Wed Mar 13 22:48:16 2002 Delivered-To: freebsd-current@freebsd.org Received: from obsecurity.dyndns.org (adsl-64-165-226-239.dsl.lsan03.pacbell.net [64.165.226.239]) by hub.freebsd.org (Postfix) with ESMTP id 8A96A37B417 for ; Wed, 13 Mar 2002 22:48:13 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id E958666C76; Wed, 13 Mar 2002 22:48:12 -0800 (PST) Date: Wed, 13 Mar 2002 22:48:12 -0800 From: Kris Kennaway To: David Greenman Cc: Kris Kennaway , John Indra , freebsd-current@FreeBSD.ORG, Alfred Perlstein Subject: Re: malloc() and the stock Perl in -CURRENT (and -STABLE) Message-ID: <20020313224812.A21067@xor.obsecurity.org> References: <20020314104525.B8244@office.naver.co.id> <20020314052810.GH74829@elvis.mu.org> <20020314124729.E8244@office.naver.co.id> <20020313223647.A20636@xor.obsecurity.org> <20020313224208.K27616@nexus.root.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="W/nzBZO5zC0uMSeA" Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <20020313224208.K27616@nexus.root.com>; from dg@root.com on Wed, Mar 13, 2002 at 10:42:08PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --W/nzBZO5zC0uMSeA Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Mar 13, 2002 at 10:42:08PM -0800, David Greenman wrote: > >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 -C= URRENT > >> and -STABLE (and I don't even know whether it's even "wrong"). All I w= ant is > >> to let the Perl maintainer in -CURRENT and -STABLE to compile the stoc= k 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? >=20 > If you read the bug report, you'll see that using perl's malloc result= s in > the program running more than 10 times faster. Yah, that program..phk seems to be saying that he believes the malloc usage pattern is atypical for applications in general, so it's conceivable that there are also other common usage patterns within perl which would be optimized by phkmalloc and not by the internal malloc. It should be benchmarked more thoroughly before the switch is made; there's only one datapoint at the moment, which isn't enough to decide whether it's a net win. Kris --W/nzBZO5zC0uMSeA 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 iD8DBQE8kEesWry0BWjoQKURAmJhAJ4t5SculzALxCTj+vkvZh+Fyu8rswCfbG2s pVidPzZj+xsE+/PbG/o7wB4= =f3Up -----END PGP SIGNATURE----- --W/nzBZO5zC0uMSeA-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message