From: Patrick Mansfield <patmans@us.ibm.com>
To: George Magklaras <george.magklaras@biotek.uio.no>
Cc: Xose Vazquez Perez <xose@wanadoo.es>, linux-scsi@vger.kernel.org
Subject: Re: SCSI Disk layer performance
Date: Thu, 29 Jan 2004 07:55:17 -0800 [thread overview]
Message-ID: <20040129075516.A1830@beaverton.ibm.com> (raw)
In-Reply-To: <4018FC0A.3050309@biotek.uio.no>; from george.magklaras@biotek.uio.no on Thu, Jan 29, 2004 at 01:26:50PM +0100
On Thu, Jan 29, 2004 at 01:26:50PM +0100, George Magklaras wrote:
> The 2.4.21-9EL might have clever things backported into it, but it is
> still missing essential things that can make a difference in the block
> layer, like an anticipatory I/O schedule. My impression is that all
> 2.4 kernels use the Linus Elevator. That works well with moderate SMP
> loads, but it does not perform well on my large-ish Hardware RAID0
> 1.1Tbyte ext3 partition on a Power Vault 220S with a Dell PERC4 host
> adapter. The 2.6.1 does work a lot more better in that sense, giving
> me an average read of 90 Mbytes/sec as opposed to
> 60+somethingMbytes/sec I used to get before with 2.4.21-9ELsmp.
>
> The new I/O schedulers (let alone driver maturity issues) are the way
> to go for maximum performance! I won't place -for the moment- a 2.6 on
> a production grade system, but in a couple of releases, I will put 2.4
> in the museum :-) with respect to SCSI I/O performance.
How does the anticipatory scheduler compare to the deadline scheduler on
your system?
What types of IO are you doing?
-- Patrick Mansfield
next prev parent reply other threads:[~2004-01-29 15:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-22 16:17 SCSI Disk layer performance Xose Vazquez Perez
2004-01-29 12:26 ` George Magklaras
2004-01-29 15:55 ` Patrick Mansfield [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-01-21 21:31 Chris Worley
2004-01-22 13:57 ` Christoph Hellwig
2004-01-23 11:02 ` Fabien Salvi
2004-01-29 18:59 ` Christoph Hellwig
2004-02-02 18:23 ` Doug Ledford
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=20040129075516.A1830@beaverton.ibm.com \
--to=patmans@us.ibm.com \
--cc=george.magklaras@biotek.uio.no \
--cc=linux-scsi@vger.kernel.org \
--cc=xose@wanadoo.es \
/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.