From owner-freebsd-arch@FreeBSD.ORG  Mon May 14 12:30:28 2007
Return-Path: <owner-freebsd-arch@FreeBSD.ORG>
X-Original-To: freebsd-arch@freebsd.org
Delivered-To: freebsd-arch@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52])
	by hub.freebsd.org (Postfix) with ESMTP id 0CA8C16A405;
	Mon, 14 May 2007 12:30:28 +0000 (UTC)
	(envelope-from rwatson@FreeBSD.org)
Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42])
	by mx1.freebsd.org (Postfix) with ESMTP id 9ECF013C44C;
	Mon, 14 May 2007 12:30:27 +0000 (UTC)
	(envelope-from rwatson@FreeBSD.org)
Received: from fledge.watson.org (fledge.watson.org [209.31.154.41])
	by cyrus.watson.org (Postfix) with ESMTP id 384A1471CF;
	Mon, 14 May 2007 08:30:26 -0400 (EDT)
Date: Mon, 14 May 2007 13:30:26 +0100 (BST)
From: Robert Watson <rwatson@FreeBSD.org>
X-X-Sender: robert@fledge.watson.org
To: Ivan Voras <ivoras@fer.hr>
In-Reply-To: <46478C9A.9050807@fer.hr>
Message-ID: <20070514132901.X24765@fledge.watson.org>
References: <20070512153532.GQ21795@elvis.mu.org>
	<63984.1178992555@critter.freebsd.dk>
	<f25m78$ik$2@sea.gmane.org> <20070513215442.GZ21795@elvis.mu.org>
	<46478C9A.9050807@fer.hr>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: Alfred Perlstein <alfred@freebsd.org>, freebsd-arch@freebsd.org
Subject: Re: HEADS DOWN
X-BeenThere: freebsd-arch@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussion related to FreeBSD architecture <freebsd-arch.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
	<mailto:freebsd-arch-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-arch>
List-Post: <mailto:freebsd-arch@freebsd.org>
List-Help: <mailto:freebsd-arch-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
	<mailto:freebsd-arch-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 14 May 2007 12:30:28 -0000


On Mon, 14 May 2007, Ivan Voras wrote:

> (This being said, since I'm not going to create a malloc implementation any 
> time soon, it of course depends on the particular author what will or will 
> not be supported :) ).
>
>> And since our allocator is vastly superior
>
> phkmalloc isn't any more and it remains to be seen for jemalloc :)

Actually, competitive MySQL benchmarking against Linux seems to illustrate 
that jemalloc is dramatically more scalable than the native glibc malloc, and 
comparable with the google malloc.  I have to admit, however, that I do wish 
we'd retained an easy switch to let us go back and forth between phkmalloc and 
jemalloc for comparison purposes.

Robert N M Watson
Computer Laboratory
University of Cambridge