public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: Mike Anderson <andmike@us.ibm.com>
Cc: Dave Hansen <haveblue@us.ibm.com>,
	"Bond, Andrew" <Andrew.Bond@hp.com>,
	linux-kernel@vger.kernel.org
Subject: Re: TPC-C benchmark used standard RH kernel
Date: Fri, 20 Sep 2002 19:31:03 +0200	[thread overview]
Message-ID: <20020920173103.GK936@suse.de> (raw)
In-Reply-To: <20020920172041.GB1944@beaverton.ibm.com>

On Fri, Sep 20 2002, Mike Anderson wrote:
> 
> Dave Hansen [haveblue@us.ibm.com] wrote:
> > Bond, Andrew wrote:
> > > This isn't as recent as I would like, but it will give you an idea.
> > > Top 75 from readprofile.  This run was not using bigpages though.
> > >
> > > 00000000 total                                      7872   0.0066
> > > c0105400 default_idle                               1367  21.3594
> > > c012ea20 find_vma_prev                               462   2.2212
> 
> > > c0142840 create_bounce                               378   1.1250
> > > c0142540 bounce_end_io_read                          332   0.9881
> 
> .. snip..
> > 
> > Forgive my complete ignorane about TPC-C...  Why do you have so much 
> > idle time?  Are you I/O bound? (with that many disks, I sure hope not 
> > :) )  Or is it as simple as leaving profiling running for a bit before 
> > or after the benchmark was run?
> 
> The calls to create_bounce and bounce_end_io_read are indications that
> some of your IO is being bounced and will not be running a peak
> performance. 
> 
> This is avoided by using the highmem IO changes which I believe are not
> in the standard RH kernel. Unknown if that would address your idle time
> question.

They benched RHAS iirc, and that has the block-highmem patch. They also
had more than 4GB of memory, alas, there is bouncing. That doesn't work
on all hardware, and all drivers.

-- 
Jens Axboe


  reply	other threads:[~2002-09-20 17:26 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-19 19:27 TPC-C benchmark used standard RH kernel Bond, Andrew
2002-09-19 20:40 ` Dave Hansen
2002-09-20 17:20   ` Mike Anderson
2002-09-20 17:31     ` Jens Axboe [this message]
2002-09-20 18:05       ` Mike Anderson
2002-09-20 20:56 ` William Lee Irwin III
2002-09-20 22:07   ` Martin J. Bligh
  -- strict thread matches above, loose matches on Subject: below --
2002-09-20 17:43 Bond, Andrew
2002-09-19 21:18 Bond, Andrew
2002-09-19 21:48 ` Dave Hansen
2002-09-19 19:15 Bond, Andrew
2002-09-19 17:15 Bond, Andrew
2002-09-19 18:14 ` Dave Hansen
2002-09-19 19:05 ` Martin J. Bligh

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=20020920173103.GK936@suse.de \
    --to=axboe@suse.de \
    --cc=Andrew.Bond@hp.com \
    --cc=andmike@us.ibm.com \
    --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