From: David Chinner <dgc@sgi.com>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: David Chinner <dgc@sgi.com>, Christoph Lameter <clameter@sgi.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [REGRESSION] 2.6.19/2.6.20-rc3 buffered write slowdown
Date: Thu, 11 Jan 2007 12:24:04 +1100 [thread overview]
Message-ID: <20070111012404.GW33919298@melbourne.sgi.com> (raw)
In-Reply-To: <45A58DFA.8050304@yahoo.com.au>
On Thu, Jan 11, 2007 at 12:08:10PM +1100, Nick Piggin wrote:
> David Chinner wrote:
> >Sure, but that doesn't really show the how erratic the per-filesystem
> >throughput is because the test I'm running is PCI-X bus limited in
> >it's throughput at about 750MB/s. Each dm device is capable of about
> >340MB/s write, so when one slows down, the others will typically
> >speed up.
>
> But you do also get aggregate throughput drops? (ie. 2.6.20-rc3-worse)
Yes - you can see that from the vmstat output I sent.
At 500GB into the write of each file (about 60% of the disks filled)
the per fs write rate should be around 220MB/s, so aggregate should
be around 650MB/s. That's what Im seeing with 2.6.18 and 2.6.20-rc3
with a tweaked dirty_ratio. Without the dirty_ratio tweak, you see
what is in 2.6.20-rc3-worse.
e.g. I just changed dirty ratio from 10 to 40 and I've gone from
consistent 210-215MB/s per filesystm (~630-650MB/s aggregate) to
ranging over 110-200MB/s per fielsystem and aggregates of ~450-600MB/s.
I changed dirty_ratio back to 10, and within 15 seconds we are back
to consistent 210MB/s per filesystem and 630-650MB/s write.
> >So, what I've attached is three files which have both
> >'vmstat 5' output and 'iostat 5 |grep dm-' output in them.
>
> Ahh, sorry to be unclear, I meant:
>
> cat /proc/vmstat > pre
> run_test
> cat /proc/vmstat > post
Ok, I'll get back to you on that one - even at 600+MB/s, writing 5TB
of data takes some time....
Cheers,
Dave.
--
Dave Chinner
Principal Engineer
SGI Australian Software Group
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2007-01-11 1:24 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-10 22:37 David Chinner
2007-01-10 23:04 ` Christoph Lameter
2007-01-10 23:08 ` David Chinner
2007-01-10 23:12 ` Christoph Lameter
2007-01-10 23:18 ` David Chinner
2007-01-10 23:13 ` Nick Piggin
2007-01-11 0:31 ` David Chinner
2007-01-11 0:43 ` Christoph Lameter
2007-01-11 1:06 ` David Chinner
2007-01-11 1:40 ` Christoph Lameter
2007-01-11 2:57 ` David Chinner
2007-01-11 1:08 ` Nick Piggin
2007-01-11 1:24 ` David Chinner [this message]
2007-01-11 9:27 ` Nick Piggin
2007-01-11 17:51 ` Christoph Lameter
2007-01-12 0:06 ` Nick Piggin
2007-01-12 3:04 ` Christoph Lameter
[not found] ` <20070111063555.GB33919298@melbourne.sgi.com>
2007-01-11 9:23 ` Nick Piggin
2007-01-11 1:11 ` David Chinner
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=20070111012404.GW33919298@melbourne.sgi.com \
--to=dgc@sgi.com \
--cc=clameter@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=nickpiggin@yahoo.com.au \
/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