From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Diego Calleja <diegocg@gmail.com>
Cc: "Stephen Cuppett" <cuppett@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: Performance versus FreeBSD 7.0
Date: Tue, 4 Mar 2008 00:04:51 +1100 [thread overview]
Message-ID: <200803040004.52299.nickpiggin@yahoo.com.au> (raw)
In-Reply-To: <20080229155408.116fa5a1.diegocg@gmail.com>
On Saturday 01 March 2008 01:54, Diego Calleja wrote:
> El Fri, 29 Feb 2008 08:38:00 -0500, "Stephen Cuppett" <cuppett@gmail.com>
escribió:
> > loads and 1500% at high loads. When compared with the best performing
> > Linux kernel (2.6.22 or 2.6.24) performance is 15% better. Results are
>
> There has been some performance problems with sysbench performance in linux
> which made it slower than freebsd, there were some patches to speed things
> up, not sure if they have been merged.
There definitely were performance problems with threaded malloc/free
in the Linux kernel and glibc. Fixes have been merged in both packages,
and AFAIK the FreeBSD guys tested with those fixes in place.
I think these were never really run into before in part due to MySQL's
unscalable heap design makes it not scale well on higher numbers of
CPUs anyway, and also made the malloc problems more pronounced (ie.
they added a bit to the contention of the single heap lock, which is
the big killer here).
But it was very nice to be made aware of the problem and be able to
improve it.
> Myself I find fun that they look at Linux as the Leader That Must Be
> Surpassed. All the performance highlights of freebsd 7.0 are things that
> linux already did some years ago.
I don't know very much about FreeBSD nor have verified the results
for myself. But to their credit they seem to have done quite well at
least on the smaller end of the scale.
next prev parent reply other threads:[~2008-03-03 13:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-29 13:38 Performance versus FreeBSD 7.0 Stephen Cuppett
2008-02-29 14:54 ` Diego Calleja
2008-03-03 13:04 ` Nick Piggin [this message]
2008-03-03 19:02 ` Cyrus Massoumi
2008-03-03 19:24 ` Nick Piggin
2008-03-03 22:47 ` Cyrus Massoumi
2008-03-03 23:23 ` Andi Kleen
2008-03-04 5:51 ` Cyrus Massoumi
2008-03-06 12:53 ` Nick Piggin
2008-03-06 13:12 ` Andi Kleen
2008-03-03 12:34 ` Andi Kleen
2008-03-06 17:29 ` debian developer
2008-03-06 17:34 ` debian developer
[not found] <a2dDb-60y-29@gated-at.bofh.it>
[not found] ` <a2eSt-7UK-1@gated-at.bofh.it>
2009-01-25 10:07 ` Lx
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200803040004.52299.nickpiggin@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=cuppett@gmail.com \
--cc=diegocg@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox