Date: Wed, 14 Jan 2004 08:47:07 -0500 From: "Robin P. Blanchard" <robin.blanchard@gactr.uga.edu> To: <current@freebsd.org> Subject: RE: perl malloc slow? Message-ID: <EE3D3FBAFFCAED448C21C398FDAD91AC013BDE3C@EBE1.gc.nat>
next in thread | raw e-mail | index | archive | help
> -----Original Message----- > From: owner-freebsd-current@freebsd.org=20 > [mailto:owner-freebsd-current@freebsd.org] On Behalf Of Holger Kipp > Sent: Wednesday, January 14, 2004 6:51 AM > To: kris@obsecurity.org; des@des.no > Cc: stable@freebsd.org; current@freebsd.org > Subject: Re: perl malloc slow? >=20 > Kris Kennaway (kris@obsecurity.org) wrote:=20 > > > >> This is basically a bug in Perl (poor choice of algorithm=20 > for growing=20 > >> strings). Perl's malloc() implementation knows about and=20 > compensates=20 > >> for this bug. FreeBSD's malloc() implementation does not. >=20 > >I heard someone say it was fixed in perl 5.<mumble> (8?) >=20 > As I now know, at least the perl(5.8.2) port is build with=20 > perl malloc as default. >=20 > Sorry for starting this thread - but I learned a lot about=20 > malloc this way ;-) and with perl v5.8.2 performance is very=20 > good again! Just another piece of possible useful information for the list... Building mod_perl2-1.99r12 against perl-5.6.1_15 with -DWITH_PERL_MALLOC causes apache2 to core dump; without -DWITH_PERL_MALLOC, all's well. --------------------------------------- Robin P. Blanchard Systems Integration Specialist Georgia Center for Continuing Education fon: 706.542.2404 < > fax: 706.542.6546 ---------------------------------------
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?EE3D3FBAFFCAED448C21C398FDAD91AC013BDE3C>