From owner-freebsd-stable@FreeBSD.ORG Thu Oct 5 11:27:37 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C85C516A407 for ; Thu, 5 Oct 2006 11:27:37 +0000 (UTC) (envelope-from dudu@dudu.ro) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1D2F643D45 for ; Thu, 5 Oct 2006 11:27:25 +0000 (GMT) (envelope-from dudu@dudu.ro) Received: by py-out-1112.google.com with SMTP id o67so658640pye for ; Thu, 05 Oct 2006 04:27:24 -0700 (PDT) Received: by 10.64.210.7 with SMTP id i7mr2045075qbg; Thu, 05 Oct 2006 04:27:24 -0700 (PDT) Received: by 10.65.225.13 with HTTP; Thu, 5 Oct 2006 04:27:24 -0700 (PDT) Message-ID: Date: Thu, 5 Oct 2006 14:27:24 +0300 From: "Vlad GALU" To: freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: Is jemalloc going to make its way into RELENG_6? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Oct 2006 11:27:37 -0000 Judging from my tests (allocating numerous small objects, then freeing the memory) it looks like the bottleneck is in free(). I've built a different libc library with the malloc.c and tree.h taken from HEAD and it now behaves nicely. I haven't seen any bad side effects on this machine (it's the lappie I do most of my work on, I run KDE, seamonkey, mplayer, openoffice, the like) since I switched to the new libc. Another nice solution would be to ship the modified libc in base so the people who really need jemalloc can relink to it via libmap.conf. -- If it's there, and you can see it, it's real. If it's not there, and you can see it, it's virtual. If it's there, and you can't see it, it's transparent. If it's not there, and you can't see it, you erased it.