From: "Chen, Kenneth W" <kenneth.w.chen@intel.com>
To: "'Linus Torvalds'" <torvalds@osdl.org>
Cc: "'Andrew Morton'" <akpm@osdl.org>, <linux-kernel@vger.kernel.org>
Subject: RE: Industry db benchmark result on recent 2.6 kernels
Date: Tue, 29 Mar 2005 16:22:20 -0800 [thread overview]
Message-ID: <200503300022.j2U0MKg03222@unix-os.sc.intel.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0503291546180.6036@ppc970.osdl.org>
On Mon, 28 Mar 2005, Chen, Kenneth W wrote:
> With that said, here goes our first data point along with some historical data
> we have collected so far.
>
> 2.6.11 -13%
> 2.6.9 - 6%
> 2.6.8 -23%
> 2.6.2 - 1%
> baseline (rhel3)
Linus Torvalds wrote on Tuesday, March 29, 2005 4:00 PM
> How repeatable are the numbers across reboots with the same kernel? Some
> benchmarks will depend heavily on just where things land in memory,
> especially with things like PAE or even just cache behaviour (ie if some
> frequenly-used page needs to be kmap'ped or not depending on where it
> landed).
Very repeatable. This workload is very steady and resolution in throughput
is repeatable down to 0.1%. We toss everything below that level as noise.
> You don't have the PAE issue on ia64, but there could be other issues.
> Some of them just disk-layout issues or similar, ie performance might
> change depending on where on the disk the data is written in relationship
> to where most of the reads come from etc etc. The fact that it seems to
> fluctuate pretty wildly makes me wonder how stable the numbers are.
This workload has been around for 10+ years and people at Intel studied the
characteristics of this workload inside out for 10+ years. Every stones will
be turned at least more than once while we tune the entire setup making sure
everything is well balanced. And we tune the system whenever there is a
hardware change. Data layout on the disk spindle are very well balanced.
> Also, it would be absolutely wonderful to see a finer granularity (which
> would likely also answer the stability question of the numbers). If you
> can do this with the daily snapshots, that would be great. If it's not
> easily automatable, or if a run takes a long time, maybe every other or
> every third day would be possible?
I sure will make my management know that Linus wants to see the performance
number on a daily bases (I will ask for a couple of million dollar to my
manager for this project :-))
next prev parent reply other threads:[~2005-03-30 0:22 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
2005-03-30 0:00 ` Linus Torvalds
2005-03-30 0:22 ` Chen, Kenneth W [this message]
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=200503300022.j2U0MKg03222@unix-os.sc.intel.com \
--to=kenneth.w.chen@intel.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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®