From owner-freebsd-questions Sat Nov 11 16:20:23 2000 Delivered-To: freebsd-questions@freebsd.org Received: from mercury.ccmr.cornell.edu (mercury.ccmr.cornell.edu [128.84.231.97]) by hub.freebsd.org (Postfix) with ESMTP id 7C28037B479; Sat, 11 Nov 2000 16:20:21 -0800 (PST) Received: from dragon.ccmr.cornell.edu (IDENT:0@dragon.ccmr.cornell.edu [128.84.231.182]) by mercury.ccmr.cornell.edu (8.9.3/8.9.3) with ESMTP id TAA13334; Sat, 11 Nov 2000 19:20:21 -0500 Received: from localhost (mitch@localhost) by dragon.ccmr.cornell.edu (8.9.3/8.9.3) with ESMTP id TAA17412; Sat, 11 Nov 2000 19:20:19 -0500 X-Authentication-Warning: dragon.ccmr.cornell.edu: mitch owned process doing -bs Date: Sat, 11 Nov 2000 19:20:19 -0500 (EST) From: Mitch Collinsworth To: Dan Nelson Cc: Doug Barton , freebsd-questions@FreeBSD.ORG, Mitch Collinsworth Subject: Re: Linux malloc better on FreeBSD than FreeBSD malloc? In-Reply-To: <20001111171033.A21628@dan.emsphone.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > None of this explains however, why the > > > Linux binary running on FreeBSD was able to do what the FreeBSD > > > binary could not. That was my first question. > > > You might want to try installing the "libdlmalloc" port, linking with > that, and re-running your FreeBSD test; dlmalloc implements > mmap()-based allocation for large requests. Well this seems to make a significant difference. Using libdlmalloc and still not having done any kernel tuning, I'm now getting the same results from the FreeBSD binary as the Linux binary. Ok, that at least solves the first question. Now I'll move on to tuning. -Mitch To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message