From: Chris Mason <chris.mason@oracle.com>
To: Chris Mason <chris.mason@oracle.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: compilebench numbers for ext4
Date: Mon, 22 Oct 2007 19:48:54 -0400 [thread overview]
Message-ID: <20071022194854.0c98d583@think.oraclecorp.com> (raw)
In-Reply-To: <20071022193104.0beafeca@think.oraclecorp.com>
On Mon, 22 Oct 2007 19:31:04 -0400
Chris Mason <chris.mason@oracle.com> wrote:
> I did expect delayed allocation to help the write phases of
> compilebench, especially the parts where it writes out .o files in
> random order (basically writing medium sized files all over the
> directory tree). But, every phase except reads showed huge
> improvements.
>
> http://oss.oracle.com/~mason/compilebench/ext4/ext-create-compare.png
> http://oss.oracle.com/~mason/compilebench/ext4/ext-compile-compare.png
> http://oss.oracle.com/~mason/compilebench/ext4/ext-read-compare.png
> http://oss.oracle.com/~mason/compilebench/ext4/ext-rm-compare.png
This might make the IO during reads a little easier to see. The dirs
will look like the kernel after a make -j. So each directory will have
a bunch of small .c files that are close together and a bunch of .o
files that are randomly created across the tree.
http://oss.oracle.com/~mason/compilebench/ext4/ext4-read.mpg
-chris
next prev parent reply other threads:[~2007-10-22 23:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-22 23:31 compilebench numbers for ext4 Chris Mason
2007-10-22 23:48 ` Chris Mason [this message]
2007-10-23 0:12 ` Mingming Cao
2007-10-23 0:54 ` Chris Mason
2007-10-23 12:43 ` Aneesh Kumar K.V
2007-10-23 13:08 ` Chris Mason
2007-10-23 13:42 ` Aneesh Kumar K.V
2007-10-25 15:34 ` Jose R. Santos
2007-10-25 18:43 ` Chris Mason
2007-10-25 22:40 ` Jose R. Santos
2007-10-25 23:45 ` Chris Mason
2007-10-25 15:54 ` Jose R. Santos
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=20071022194854.0c98d583@think.oraclecorp.com \
--to=chris.mason@oracle.com \
--cc=linux-ext4@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).