All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Hansen <haveblue@us.ibm.com>
To: "Bond, Andrew" <Andrew.Bond@hp.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: TPC-C benchmark used standard RH kernel
Date: Thu, 19 Sep 2002 11:14:53 -0700	[thread overview]
Message-ID: <3D8A141D.2080809@us.ibm.com> (raw)
In-Reply-To: 45B36A38D959B44CB032DA427A6E106402D09E42@cceexc18.americas.cpqcorp.net

Bond, Andrew wrote:
 > I believe I need to clarify my earlier posting about kernel features that
 > gave the benchmark a boost.  The kernel that we used in the benchmark was an
 > unmodified Red Hat Advanced Server 2.1 kernel.  We did tune the kernel via
 > standard user space tuning, but the kernel was not patched.  HP, Red Hat, and
 > Oracle have worked closely together to make sure that the features I
 > mentioned were in the Advanced Server kernel "out of the box."

Have you done much profiling of that kernel?  I'm sure a lot of people would be 
very interested to see even readprofile results from a piece of the cluster 
during a TPC run.

-- 
Dave Hansen
haveblue@us.ibm.com


  reply	other threads:[~2002-09-19 18:10 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-19 17:15 TPC-C benchmark used standard RH kernel Bond, Andrew
2002-09-19 18:14 ` Dave Hansen [this message]
2002-09-19 19:05 ` Martin J. Bligh
  -- strict thread matches above, loose matches on Subject: below --
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=3D8A141D.2080809@us.ibm.com \
    --to=haveblue@us.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.