From: "Chen, Kenneth W" <kenneth.w.chen@intel.com>
To: "'Nick Piggin'" <nickpiggin@yahoo.com.au>,
"Andrew Morton" <akpm@osdl.org>
Cc: <mingo@elte.hu>, <linux-kernel@vger.kernel.org>
Subject: RE: [patch 0/2] fix perf. bug in wake-up load balancing for aim7 and db workload
Date: Mon, 13 Feb 2006 22:13:13 -0800 [thread overview]
Message-ID: <200602140613.k1E6DDg19350@unix-os.sc.intel.com> (raw)
In-Reply-To: <43F15211.2090206@yahoo.com.au>
Nick Piggin wrote on Monday, February 13, 2006 7:44 PM
> Andrew Morton wrote:
> > Well I don't see any benchmark numbers in the original patch. Just an
> > assertion that it "should" help something.
> >
> The regression was in a Ken's commercial database benchmark. I couldn't
> reproduce it but presumably it did fix it otherwise Ken would would have
> piped up?
I wasn't entirely happy though ;-)
> > I'm more inclined to revert it and not add the sysctl (ugh) until we have a
> > good reason to do so.
> >
>
> If you revert this then Ken's database benchmark gets worse. Hence the
> sysctl.
Yes, Nick is correct. For db workload, the wake-ups type are mixed.
Some of them are random, some of them are not because we do interrupt
binding. The break down between random/fixed is about 30/70. Thus,
Nick's patch helps 30% of time. With sysctl, we can regain the entire
up side for db workload while retain workload on the other end of
spectrum.
- Ken
next prev parent reply other threads:[~2006-02-14 6:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-14 3:09 Chen, Kenneth W
2006-02-14 3:38 ` Andrew Morton
2006-02-14 3:44 ` Nick Piggin
2006-02-14 3:57 ` Nick Piggin
2006-02-14 4:13 ` Andrew Morton
2006-02-14 3:59 ` Andrew Morton
2006-02-14 6:13 ` Chen, Kenneth W [this message]
2006-02-14 5:47 ` Chen, Kenneth W
2006-02-14 7:34 ` Ingo Molnar
2006-02-14 7:46 Chen, Kenneth W
2006-02-14 8:00 ` Andrew Morton
2006-02-14 12:47 ` Ingo Molnar
2006-02-14 18:31 ` Chen, Kenneth W
2006-02-14 8:04 Chen, Kenneth W
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=200602140613.k1E6DDg19350@unix-os.sc.intel.com \
--to=kenneth.w.chen@intel.com \
--cc=akpm@osdl.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®