From: Jon Burgess <lkml@jburgess.uklinux.net>
To: Andrew Morton <akpm@osdl.org>
Cc: Jon Burgess <lkml@jburgess.uklinux.net>, linux-kernel@vger.kernel.org
Subject: Re: ext2/3 performance regression in 2.6 vs 2.4 for small interleaved writes
Date: Fri, 13 Feb 2004 12:35:58 +0000 [thread overview]
Message-ID: <402CC4AE.7050904@jburgess.uklinux.net> (raw)
In-Reply-To: <20040212015626.48631555.akpm@osdl.org>
Andrew Morton wrote:
>What filesytem was that with?
>
>
I re-ran the tests again last night and founfd that I had made one
mistake in my description.
The really poor results occured with the *ext3* filesystem, not ext2.
"mount" was telling me that the contents of /etc/fstab which was ext2 -
but the kernel actually had it mounted it as ext3.
I think I might be able to give a little insight to the "0.34MB/s" and
"0.48MB/s" numbers. I think these numbers closely match the theoretical
performance rate when a single 4kB write occurs per disk rotation.
4kB * 5400RPM / 60 seconds = 360 kB/s
4kB * 7200RPM / 60 seconds = 480 kB/s
Perhaps the drives that I am running the test on do not have
write-caching enabled.
By the time the first 4kB write has completed the drive may need to wait
a complete rotation before it can do the next write. I don't think it
quite explains the difference between ext2 and ext3. Any ideas?
Below are the resuls of ext2/ext3 tests on a new Seagate 80Gb SATA, 8MB
Cache, model ST380023AS.
The ext3 results are a lot better, perhaps this drive has write caching
enabled.
Num streams |1 1 |2 2 |4 4
Filesystem |Write Read |Write Read |Write Read
------------------------------|--------------|--------------
Ext2 |40.17 43.07 |10.88 21.49 |10.13 11.41
ext3-journal |16.06 42.24 | 7.56 16.28 | 7.17 11.25
ext3-ordered |37.31 43.12 | 4.64 15.33 | 5.25 11.28
ext3-writeback |37.33 42.93 | 4.00 14.88 | 2.97 11.26
Jon
next prev parent reply other threads:[~2004-02-13 12:36 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-11 19:04 ext2/3 performance regression in 2.6 vs 2.4 for small interleaved writes Jon Burgess
2004-02-11 20:28 ` Rik van Riel
2004-02-11 21:02 ` Michael Frank
2004-02-11 21:18 ` Diego Calleja
2004-02-12 2:00 ` Dave Olien
2004-02-12 2:23 ` Andrea Arcangeli
2004-02-12 9:42 ` ext2/3 performance regression in 2.6 vs 2.4 for small interl Giuliano Pochini
2004-02-12 10:15 ` John Bradford
2004-02-12 10:27 ` Nick Piggin
2004-02-12 17:05 ` Michael Frank
2004-02-12 17:18 ` Valdis.Kletnieks
2004-02-12 20:55 ` Helge Hafting
2004-02-13 1:57 ` Jamie Lokier
2004-02-13 2:05 ` Nick Piggin
2004-02-12 14:59 ` Andrea Arcangeli
2004-02-13 12:15 ` ext2/3 performance regression in 2.6 vs 2.4 for small interleaved writes Jon Burgess
2004-02-12 10:40 ` Jon Burgess
2004-02-12 20:17 ` Hans Reiser
2004-02-12 9:56 ` Andrew Morton
2004-02-12 20:20 ` Jon Burgess
2004-02-13 8:28 ` Juan Piernas Canovas
2004-02-16 17:51 ` Alex Zarochentsev
2004-02-16 20:03 ` Jon Burgess
2004-02-13 12:35 ` Jon Burgess [this message]
2004-02-14 15:00 ` Jon Burgess
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=402CC4AE.7050904@jburgess.uklinux.net \
--to=lkml@jburgess.uklinux.net \
--cc=akpm@osdl.org \
--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