From: Dave Hansen <haveblue@us.ibm.com>
To: Peter Wong <wpeter@us.ibm.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@digeo.com>,
Mike Sullivan <mksully@us.ibm.com>,
Bill Hartner <bhartner@us.ibm.com>,
Ray Venditti <venditti@us.ibm.com>
Subject: Re: Evaluation of three I/O schedulers
Date: 30 Jun 2003 08:15:51 -0700 [thread overview]
Message-ID: <1056986151.25479.3.camel@nighthawk> (raw)
In-Reply-To: <OF9393D547.0D1D003C-ON85256D55.004DFAA4@pok.ibm.com>
On Mon, 2003-06-30 at 07:21, Peter Wong wrote:
> The 8-way machine has Pentium 4 2.0 GHz processors, 16 GB physical
> memory, 2MB L3 cache, 8 FC controllers with 80 disks. Hyperthreading
> was turned on for the three runs. The CPU utilization is similar for all
> three runs: 65% user, 7% system and 28% idle.
Could you give us an idea of how greatly utilized your 10 fiber
controllers are? What about memory? Would a larger readahead be
beneficial?
--
Dave Hansen
haveblue@us.ibm.com
next prev parent reply other threads:[~2003-06-30 15:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-30 14:21 Evaluation of three I/O schedulers Peter Wong
2003-06-30 15:15 ` Dave Hansen [this message]
2003-07-01 6: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=1056986151.25479.3.camel@nighthawk \
--to=haveblue@us.ibm.com \
--cc=akpm@digeo.com \
--cc=bhartner@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mksully@us.ibm.com \
--cc=venditti@us.ibm.com \
--cc=wpeter@us.ibm.com \
/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