From owner-freebsd-current@FreeBSD.ORG  Wed Jan 14 03:51:38 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id C371216A4CE; Wed, 14 Jan 2004 03:51:38 -0800 (PST)
Received: from alogis.com (firewall.solit-ag.de [212.184.102.1])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 55BF743D64; Wed, 14 Jan 2004 03:51:36 -0800 (PST)
	(envelope-from Holger.Kipp@alogis.com)
Received: from intserv.int1.b.intern (localhost [127.0.0.1])
	by alogis.com (8.11.1/8.9.3) with SMTP id i0EBpPY94333;
	Wed, 14 Jan 2004 12:51:26 +0100 (CET)
	(envelope-from hk@alogis.com)
Message-Id: <200401141151.i0EBpPY94333@alogis.com>
Date: Wed, 14 Jan 2004 11:51:20 +0000
From: Holger Kipp <Holger.Kipp@alogis.com>
To: kris@obsecurity.org, des@des.no
X-Mailer: phpGroupWare (http://www.phpgroupware.org)
MIME-version: 1.0
Content-type: text/plain; charset="iso-8859-1"
Content-Disposition: inline
Content-description: Mail message body
cc: stable@freebsd.org
cc: current@freebsd.org
Subject: Re: perl malloc slow?
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
Reply-To: Holger.Kipp@alogis.com
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Jan 2004 11:51:38 -0000



Kris Kennaway (kris@obsecurity.org) wrote: 
>
>> This is basically a bug in Perl (poor choice of algorithm for growing
>> strings).  Perl's malloc() implementation knows about and compensates
>> for this bug.  FreeBSD's malloc() implementation does not.

>I heard someone say it was fixed in perl 5.<mumble> (8?)

As I now know, at least the perl(5.8.2) port is build with perl malloc as
default.

Sorry for starting this thread - but I learned a lot about malloc this way ;-)
and with perl v5.8.2 performance is very good again!

Thanx for all who replied!


Regards,
Holger