From: "Chen, Kenneth W" <kenneth.w.chen@intel.com>
To: <linux-kernel@vger.kernel.org>
Subject: Update: Industry db benchmark result
Date: Wed, 22 Jun 2005 14:15:56 -0700 [thread overview]
Message-ID: <200506222115.j5MLFtg10364@unix-os.sc.intel.com> (raw)
It's been awhile since last time I reported Linux kernel performance
for an industry standard transaction processing database benchmark. It's
time to report the data again to keep everyone informed. Here is the
latest result that we measured (4P 1.6GHz ia64, 9M L3 cache, 64GB memory,
480 15K-RPM disks).
2.4.21-4.EL baseline
2.6.9 - 6.00%
2.6.11 -13.00%
2.6.12-rc3 -13.54%
2.6.12-rc4 -13.05%
2.6.12-rc5 -12.86%
2.6.12-rc6 -12.66%
It's been hovering around -13%. I will take a measurement of 2.6.12, though
I don't expect it to deviate too far from 2.6.12-rc6. There are 718 patches
committed since 2.6.12 as of 6/22 14:09 PDT, so I'm going to take a snapshot
today or tomorrow and queue it up for benchmark measurement. I will probably
take all the scheduler patches currently in -mm and give that a whirl as well.
- Ken
next reply other threads:[~2005-06-22 21:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-22 21:15 Chen, Kenneth W [this message]
[not found] <200506222115.j5MLFtg10364@unix-os.sc.intel.com.suse.lists.linux.kernel>
2005-06-22 23:43 ` Andi Kleen
2005-06-23 0:09 ` 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=200506222115.j5MLFtg10364@unix-os.sc.intel.com \
--to=kenneth.w.chen@intel.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®