From: Nicholas Miell <nmiell@comcast.net>
To: Cyrus Massoumi <cyrusm@gmx.net>
Cc: Nick Piggin <nickpiggin@yahoo.com.au>,
"Molnar, Ingo" <mingo@elte.hu>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: Poor PostgreSQL scaling on Linux 2.6.25-rc5 (vs 2.6.22)
Date: Tue, 11 Mar 2008 16:12:12 -0700 [thread overview]
Message-ID: <1205277132.12854.19.camel@entropy> (raw)
In-Reply-To: <47D6FAD0.1020608@gmx.net>
On Tue, 2008-03-11 at 22:34 +0100, Cyrus Massoumi wrote:
> Nicholas Miell wrote:
>
> > (Also, ignoring MySQL because it's a terrible piece of software at least
> > when regarding it's scalability is a bad idea. It's the M in LAMP, it
> > has a huge user base, and FreeBSD manages to outperform Linux with the
> > same unscalable piece of software.)
>
> Did you actually see this?
> http://www.kernel.org/pub/linux/kernel/people/npiggin/sysbench/
>
> FreeBSD does not outperform Linux, it's actually a bit faster according
> to Nick's tests.
I am aware of those results, but in the mail I was responding to, Nick
Piggin said the following:
> The problem with MySQL contention means that if the scheduler
> unluckily chooses to deschedule a lock holder, then you can get
> idle time building up on other cores and you can get context switch
> cascades as things all pile up onto this heavily contended lock. As
> such, it means MySQL is not an ideal candidate for looking at
> performance behaviour. I discounted the relatively worse scaling of
> MySQL with 2.6.25-rc (than 2.6.22) as such an effect.
which I interpreted to mean that MySQL performs worse on 2.6.23+ than on
2.6.22 but for some reason this doesn't matter.
--
Nicholas Miell <nmiell@comcast.net>
next prev parent reply other threads:[~2008-03-11 23:12 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-11 6:49 Poor PostgreSQL scaling on Linux 2.6.25-rc5 (vs 2.6.22) Nick Piggin
2008-03-11 7:58 ` Ingo Molnar
2008-03-11 8:28 ` Nick Piggin
2008-03-11 9:59 ` Ingo Molnar
2008-03-11 21:07 ` Nicholas Miell
2008-03-11 21:34 ` Cyrus Massoumi
2008-03-11 23:12 ` Nicholas Miell [this message]
2008-03-11 23:42 ` Nick Piggin
2008-03-11 23:47 ` Stephen Hemminger
2008-03-12 9:00 ` Zhang, Yanmin
[not found] ` <20080311102538.GA30551@elte.hu>
[not found] ` <20080311120230.GA5386@elte.hu>
2008-03-12 1:21 ` Nick Piggin
2008-03-12 7:58 ` Peter Zijlstra
2008-03-17 0:44 ` Nick Piggin
2008-03-17 5:16 ` Ray Lee
2008-03-17 5:21 ` Willy Tarreau
2008-03-17 7:19 ` Nick Piggin
2008-03-17 8:26 ` Willy Tarreau
2008-03-17 8:54 ` Nick Piggin
2008-03-17 9:28 ` Peter Zijlstra
2008-03-17 9:56 ` Nick Piggin
2008-03-17 10:16 ` Ingo Molnar
2008-03-17 5:34 ` Nick Piggin
-- strict thread matches above, loose matches on Subject: below --
2008-03-14 15:42 Xose Vazquez Perez
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=1205277132.12854.19.camel@entropy \
--to=nmiell@comcast.net \
--cc=cyrusm@gmx.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=nickpiggin@yahoo.com.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.