From: Chris Mason <chris.mason@oracle.com>
To: linux-ext4@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: ext4 writepages is making tiny bios?
Date: Tue, 1 Sep 2009 14:44:50 -0400 [thread overview]
Message-ID: <20090901184450.GB7885@think> (raw)
Hello everyone,
I've been doing some benchmark runs to speed up btrfs and look at Jens'
new writeback work. One thing that really surprised me is that ext4
seems to be making 4k bios pretty much all the time.
The test I did was:
dd if=/dev/zero of=/mnt/foo bs=1M count=32768
It was done under seekwatcher, so blktrace was running. The blktrace
files for xfs and btrfs were about 60MB, but ext4 was almost 700MB. A
looks at the trace shows it is because ext4 is doing everything in 4k writes,
and I'm tracing on top of dm so the traces don't reflect any kind of
merging done by the elevator.
This graph shows the difference:
http://oss.oracle.com/~mason/seekwatcher/trace-buffered.png
When tracing on dm, seekwatcher uses the completion events for IOPs, so
the huge io rate for ext4 just comes from using smaller ios to write the
same data. Note the ext4 performance in this test is quite good, but I
think it would probably be better if it were making bigger bios.
A quick look at the code makes me think its trying to make big bios, so
I wanted to report it here in case things aren't working the way they
should.
(this version of seekwatcher isn't released yet, but you can grab it out
of the hg repo on linked from http://oss.oracle.com/~mason/seekwatcher)
-chris
next reply other threads:[~2009-09-01 18:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-01 18:44 Chris Mason [this message]
2009-09-01 20:57 ` ext4 writepages is making tiny bios? Theodore Tso
2009-09-01 21:27 ` Christoph Hellwig
2009-09-02 0:17 ` Chris Mason
2009-09-03 5:52 ` Dave Chinner
2009-09-03 16:42 ` Christoph Hellwig
2009-09-04 0:15 ` Theodore Tso
2009-09-04 7:20 ` Jens Axboe
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=20090901184450.GB7885@think \
--to=chris.mason@oracle.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@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;
as well as URLs for NNTP newsgroup(s).