From: Patrick Mansfield <patmans@us.ibm.com>
To: Andrew Morton <akpm@digeo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.5.62-mm2 slow file system writes across multiple disks
Date: Tue, 25 Feb 2003 11:24:58 -0800 [thread overview]
Message-ID: <20030225112458.A5618@beaverton.ibm.com> (raw)
In-Reply-To: <20030224204321.5016ded6.akpm@digeo.com>; from akpm@digeo.com on Mon, Feb 24, 2003 at 08:43:21PM -0800
On Mon, Feb 24, 2003 at 08:43:21PM -0800, Andrew Morton wrote:
> Patrick Mansfield <patmans@us.ibm.com> wrote:
> > I moved to 2.5.62-mm3 [I had to drop back to qlogicisp for my boot disk,
> > and run the feral drver as a module in order to boot without hanging], and
> > ran write-and-fsync with -f, with and without -o (O_DIRECT).
> Is this using an enormous request queue or really deep TCQ or something?
> I always turn TCQ off, stupid noxious thing it is.
Yes - pretty high, the feral driver is defaulting to 63 (comments there
say "FIX LATER"). Changing it to 8 gave much improved performance.
I'm on a slightly different kernel, anyway:
10 fsync writes of 200 mb to 10 separate disks, queue depth (TCQ) of 63 gave:
0.05user 37.14system 1:09.39elapsed 53%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (1986major+3228minor)pagefaults 0swaps
10 fsync writes of 200 mb to 10 separate disks, queue depth of 8 gave:
0.05user 38.56system 0:32.71elapsed 118%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (1986major+3228minor)pagefaults 0swaps
The total time dropped by almost half. vmstat numbers were much smoother.
It would be nice if a larger queue depth did not kill performance.
The larger queue depths can be nice for disk arrays with lots of cache and
(more) random IO patterns.
-- Patrick Mansfield
next prev parent reply other threads:[~2003-02-25 19:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-24 20:03 Patrick Mansfield
2003-02-24 21:53 ` Andrew Morton
2003-02-25 1:47 ` Patrick Mansfield
2003-02-25 4:43 ` Andrew Morton
2003-02-25 19:24 ` Patrick Mansfield [this message]
2003-02-26 8:44 ` Andrew Morton
2003-02-26 12:17 ` Helge Hafting
2003-02-26 17:18 ` Mike Anderson
2003-02-28 1:57 ` Patrick Mansfield
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=20030225112458.A5618@beaverton.ibm.com \
--to=patmans@us.ibm.com \
--cc=akpm@digeo.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®