From: "Martin J. Bligh" <mbligh@aracnet.com>
To: "Bond, Andrew" <Andrew.Bond@hp.com>, linux-kernel@vger.kernel.org
Subject: Re: TPC-C benchmark used standard RH kernel
Date: Thu, 19 Sep 2002 12:05:36 -0700 [thread overview]
Message-ID: <434201548.1032437133@[10.10.2.3]> (raw)
In-Reply-To: <45B36A38D959B44CB032DA427A6E106402D09E42@cceexc18.americas.cpqcorp.net>
> Could we have gotten better performance by patching the kernel? Sure. There are many new features in 2.5 that would enhance database performance. However, the fairly strict support requirements of TPC benchmarking mean that we need to benchmark a kernel that a Linux distributor ships and can support.
> Modifications could also be taken to the extreme, and we could have built a screamer kernel that runs Oracle TPC-C's and nothing else. However, that doesn't really tell us anything useful and doesn't help those customers thinking about running Linux. The question also becomes "Who would provide customer support for that kernel?"
Unofficial results for 2.5 vs 2.4 (or 2.4-redhatAS) would be most
interesting if you're able to gather them, and still have the
machine. Most times you can avoid their draconian rules by saying
"on a large benchmark test that I can't name but you all know what
it is ..." instead of naming it ... ;-)
M.
next prev parent reply other threads:[~2002-09-19 19:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-19 17:15 Bond, Andrew
2002-09-19 18:14 ` Dave Hansen
2002-09-19 19:05 ` Martin J. Bligh [this message]
2002-09-19 19:15 Bond, Andrew
2002-09-19 19:27 Bond, Andrew
2002-09-19 20:40 ` Dave Hansen
2002-09-20 17:20 ` Mike Anderson
2002-09-20 17:31 ` Jens Axboe
2002-09-20 18:05 ` Mike Anderson
2002-09-20 20:56 ` William Lee Irwin III
2002-09-20 22:07 ` Martin J. Bligh
2002-09-19 21:18 Bond, Andrew
2002-09-19 21:48 ` Dave Hansen
2002-09-20 17:43 Bond, Andrew
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='434201548.1032437133@[10.10.2.3]' \
--to=mbligh@aracnet.com \
--cc=Andrew.Bond@hp.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®