From: Chris Mason <chris.mason@oracle.com>
To: Steven Pratt <slpratt@austin.ibm.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Btrfs experimental branch updates
Date: Mon, 16 Mar 2009 21:24:49 -0400 [thread overview]
Message-ID: <1237253089.31273.4.camel@think.oraclecorp.com> (raw)
In-Reply-To: <49BD12E4.4070505@austin.ibm.com>
On Sun, 2009-03-15 at 09:38 -0500, Steven Pratt wrote:
> > Thanks for running this, but the main performance fixes for your test
> > are still in testing locally. One thing that makes a huge difference on
> > the random write run is to mount -o ssd.
> >
> >
> Tried a run with -o ssd on the raid system. It made some minor
> improvements in random write performance. Helps more on odirect, but
> mainly at the 16thread count. Single and 128 threads it doesn't make
> much difference.
>
> Results syncing now to history boxacle
> http://btrfs.boxacle.net/repository/raid/history/History.html
Well, still completely different from my test rig ;) For the random
write run, yours runs at 580 trans/sec for btrfs and mine is going along
at 8000 trans/sec.
The part that confuses me is that you seem to have some big gaps where
just a single CPU is stuck in IO wait, and not much CPU time is in use.
Do you happen to have the blktrace logs for any of the btrfs runs? I'd
be interested in a script that did sysrq-w every 5s and captured the
output.
-chris
next prev parent reply other threads:[~2009-03-17 1:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-13 15:56 Btrfs experimental branch updates Chris Mason
2009-03-13 22:52 ` Steven Pratt
2009-03-14 1:33 ` Chris Mason
2009-03-15 14:38 ` Steven Pratt
2009-03-17 1:24 ` Chris Mason [this message]
2009-03-17 20:57 ` Steven Pratt
2009-03-18 1:18 ` Chris Mason
2009-03-15 19:13 ` Grigory Makarevich
2009-03-16 13:31 ` Chris Mason
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=1237253089.31273.4.camel@think.oraclecorp.com \
--to=chris.mason@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=slpratt@austin.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