From: wbrana@gmail.com
To: Theodore Tso <tytso@mit.edu>, linux-kernel@vger.kernel.org
Subject: Re: EXT4 RAID read performance
Date: Sat, 26 Sep 2009 16:27:46 +0200 [thread overview]
Message-ID: <a769871e0909260727l65fd04a8ud49a9e0e0ec7d9a6@mail.gmail.com> (raw)
In-Reply-To: <20090919231810.GE7121@mit.edu>
On Sun, Sep 20, 2009 at 1:18 AM, Theodore Tso <tytso@mit.edu> wrote:
> You didn't say which version of the kernel you are using, which could
> be important when asking these sorts of questions about potential
> performance problems.
>
2.6.31
>
> Now, there are some workloads which compilebench might accurately
> model --- for example, tar'ing up a directory. However, despite the
> name of the benchmark, it doesn't accurately model a kernel compile.
>
You are right. I created simple benchmark which does real compilation of kernel
with following results:
reiser3
16925 msec: tar xf /usr/src/linux.tar
119173 msec: make -j4 all
ext4
14296 msec: tar xf /usr/src/linux.tar
116692 msec: make -j4 all
btrfs
13493 msec: tar xf /usr/src/linux.tar
116015 msec: make -j4 all
MD RAID10-f2 with 256 kB chunk size was used in all cases.
Source code:
http://www.sendspace.com/file/fmikv7
It depends on Qt Core library. There are hard-coded paths.
It can delete important data if it is started without customization !!!
next prev parent reply other threads:[~2009-09-26 14:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-19 18:12 wbrana
2009-09-19 22:54 ` wbrana
2009-09-19 23:18 ` Theodore Tso
2009-09-26 14:27 ` wbrana [this message]
[not found] <dmcHr-ep-7@gated-at.bofh.it>
[not found] ` <1cddc13e-c147-43e0-9b40-5e3f07941b27@e34g2000vbm.googlegroups.com>
2009-09-20 10:40 ` wbrana
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=a769871e0909260727l65fd04a8ud49a9e0e0ec7d9a6@mail.gmail.com \
--to=wbrana@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®