From: Eric Sandeen <sandeen@redhat.com>
To: surbhi.palande@canonical.com
Cc: linux-ext4@vger.kernel.org, Theodore Tso <tytso@mit.edu>
Subject: Re: ext4 performance benchmarks
Date: Wed, 20 Jan 2010 13:01:17 -0600 [thread overview]
Message-ID: <4B5752FD.40207@redhat.com> (raw)
In-Reply-To: <4B56B7FD.4080506@canonical.com>
Surbhi Palande wrote:
> Hi Guys,
>
> The following article says that ext4 performance has plummeted
> since the 2.6.31 kernel. Can someone please comment on this?
>
> http://www.phoronix.com/scan.php?page=article&item=ext4_then_now&num=1
For what it's worth, I don't put much if any stock in these benchmarks.
Against my better judgement I grepped the code to see what they actually
ran (iozone -s 2048M -i0 -i1 -f testfile AFAICT) and I saw no such
regression. Of course I don't have an atom CPU to test on ...
> Are large reads giving a lower performance for the kernels post 2.6.30?
> Is this performance attributed to some particular ext4 features/patches?
No idea what their issue is, they don't fully characterize the test
environment - at least not in a way that's easy for me to reproduce.
If the results contained the commandline that was run, the raw output,
and an archive of test environment information it'd be a big help -
otherwise we're just chasing ghosts.
(for example: did ubuntu change the default scheduler between .30
and .31? Frankly, I'm not going to go look)
In other words there's not enough context in their results to
answer your question.
> Does anyone maintain the benchmarking results for ext4 after any
> feature/big patches are applied?
It gets spot-checked, but we could always do a better job.
-Eric
prev parent reply other threads:[~2010-01-20 19:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-20 7:59 ext4 performance benchmarks Surbhi Palande
2010-01-20 19:01 ` Eric Sandeen [this message]
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=4B5752FD.40207@redhat.com \
--to=sandeen@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=surbhi.palande@canonical.com \
--cc=tytso@mit.edu \
/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).