From: "Chen, Kenneth W" <kenneth.w.chen@intel.com>
To: "'Dave Hansen'" <haveblue@us.ibm.com>
Cc: "'Andrew Morton'" <akpm@osdl.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: RE: Industry db benchmark result on recent 2.6 kernels
Date: Mon, 28 Mar 2005 12:01:06 -0800 [thread overview]
Message-ID: <200503282001.j2SK16g22781@unix-os.sc.intel.com> (raw)
In-Reply-To: <1112039416.2087.25.camel@localhost>
On Mon, 2005-03-28 at 11:33 -0800, Chen, Kenneth W wrote:
> We will be taking db benchmark measurements more frequently from now on with
> latest kernel from kernel.org (and make these measurements on a fixed interval).
> By doing this, I hope to achieve two things: one is to track base kernel
> performance on a regular base; secondly, which is more important in my opinion,
> is to create a better communication flow to the kernel developers and to keep
> all interested party well informed on the kernel performance for this enterprise
> workload.
Dave Hansen wrote on Monday, March 28, 2005 11:50 AM
> I'd guess that doing it on kernel.org is too late, sometimes. How high
> is the overhead of doing a test? Would you be able to test each -mm
> release? It's somewhat easier to toss something out of -mm for
> re-review than it is out of Linus's tree.
The overhead is fairly high to run the benchmark. It's not a one minute run.
(more or less like a 5 hour exercise. Benchmark run time along is 3+ hours).
-mm has so many stuff, I'm not sure we would have the bandwidth to do a search
on which patch trigger N% regression, etc. Let me try the base kernel first
and if resources are available, I can attempt to do it on -mm tree.
next prev parent reply other threads:[~2005-03-28 20:01 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-28 19:33 Chen, Kenneth W
2005-03-28 19:50 ` Dave Hansen
2005-03-28 20:01 ` Chen, Kenneth W [this message]
2005-03-30 0:00 ` Linus Torvalds
2005-03-30 0:22 ` Chen, Kenneth W
2005-03-30 0:46 ` Chen, Kenneth W
2005-03-30 0:57 ` Linus Torvalds
2005-03-30 1:31 ` Nick Piggin
2005-03-30 1:38 ` Chen, Kenneth W
2005-03-30 1:56 ` Nick Piggin
2005-03-31 14:14 ` Ingo Molnar
2005-03-31 19:53 ` Chen, Kenneth W
2005-03-31 20:05 ` Linus Torvalds
2005-03-31 20:08 ` Linus Torvalds
2005-03-31 22:14 ` Chen, Kenneth W
2005-03-31 23:35 ` Nick Piggin
2005-04-01 6:05 ` Paul Jackson
2005-04-01 6:34 ` Nick Piggin
2005-04-01 7:19 ` Paul Jackson
2005-04-01 6:46 ` Ingo Molnar
2005-04-01 22:32 ` Chen, Kenneth W
2005-04-01 22:51 ` Linus Torvalds
2005-04-02 2:19 ` Nick Piggin
2005-04-04 1:40 ` Kevin Puetz
2005-04-02 1:44 ` Paul Jackson
2005-04-02 2:05 ` Chen, Kenneth W
2005-04-02 2:38 ` Paul Jackson
2005-04-03 6:36 ` David Lang
2005-04-03 6:53 ` Andreas Dilger
2005-04-03 7:23 ` David Lang
2005-04-03 7:38 ` Nick Piggin
2005-04-01 6:59 ` Ingo Molnar
2005-04-01 9:29 ` Paul Jackson
2005-04-01 10:34 ` Ingo Molnar
2005-04-01 14:39 ` Paul Jackson
2005-04-01 4:52 ` Ingo Molnar
2005-04-01 5:14 ` Chen, Kenneth W
2005-04-01 22:51 ` Chen, Kenneth W
2005-04-01 16:34 Manfred Spraul
2005-04-02 1:00 Chen, Kenneth W
2005-04-02 2:12 ` Nick Piggin
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=200503282001.j2SK16g22781@unix-os.sc.intel.com \
--to=kenneth.w.chen@intel.com \
--cc=akpm@osdl.org \
--cc=haveblue@us.ibm.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
all inboxes | Powered by JetHome®