From: Chris Mason <chris.mason@oracle.com>
To: Theodore Tso <tytso@mit.edu>
Cc: Andi Kleen <andi@firstfloor.org>,
Peter Zijlstra <peterz@infradead.org>,
linux-btrfs <linux-btrfs@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: Btrfs v0.16 released
Date: Thu, 14 Aug 2008 21:10:27 -0400 [thread overview]
Message-ID: <1218762627.15342.447.camel@think.oraclecorp.com> (raw)
In-Reply-To: <20080814234458.GD13048@mit.edu>
On Thu, 2008-08-14 at 19:44 -0400, Theodore Tso wrote:
> > I spent a bunch of time hammering on different ways to fix this without
> > increasing nr_requests, and it was a mixture of needing better tuning in
> > btrfs and needing to init mapping->writeback_index on inode allocation.
> >
> > So, today's numbers for creating 30 kernel trees in sequence:
> >
> > Btrfs defaults 57.41 MB/s
> > Btrfs dup no csum 74.59 MB/s
> > Btrfs no duplication 76.83 MB/s
> > Btrfs no dup no csum no inline 76.85 MB/s
>
> What sort of script are you using? Basically something like this?
>
> for i in `seq 1 30` do
> mkdir $i; cd $i
> tar xjf /usr/src/linux-2.6.28.tar.bz2
> cd ..
> done
Similar. I used compilebench -i 30 -r 0, which means create 30 initial
kernel trees and then do nothing. compilebench simulates compiles by
writing to the FS files of the same size that you would get by creating
kernel trees or compiling them.
The idea is to get all of the IO without needing to keep 2.6.28.tar.bz2
in cache or the compiler using up CPU.
http://www.oracle.com/~mason/compilebench
-chris
next prev parent reply other threads:[~2008-08-15 1:10 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-05 19:01 Btrfs v0.16 released Chris Mason
2008-08-07 9:08 ` Peter Zijlstra
2008-08-07 10:34 ` Chris Mason
2008-08-07 14:58 ` Chris Friesen
2008-08-07 15:07 ` tvrtko.ursulin
2008-08-07 9:14 ` Peter Zijlstra
2008-08-07 10:39 ` Chris Mason
[not found] ` <3da3b5b40808070703x4cf49471q6acc00351ba019d7@mail.gmail.com>
2008-08-07 14:06 ` Chris Mason
2008-08-07 18:02 ` Andi Kleen
2008-08-08 18:48 ` Chris Mason
2008-08-08 21:56 ` Andi Kleen
2008-08-09 1:19 ` Theodore Tso
2008-08-09 1:23 ` Andi Kleen
[not found] ` <20080809012322.GF9038@one.firstfloor.org>
2008-08-09 1:43 ` Theodore Tso
2008-08-14 21:00 ` Chris Mason
2008-08-14 21:17 ` Andi Kleen
2008-08-15 1:25 ` Chris Mason
2008-08-15 1:39 ` Andi Kleen
2008-08-15 13:00 ` Chris Mason
2008-08-16 19:26 ` Szabolcs Szakacsits
2008-08-18 13:52 ` Chris Mason
2008-08-18 17:37 ` Szabolcs Szakacsits
2008-08-14 23:44 ` Theodore Tso
2008-08-15 1:10 ` Chris Mason [this message]
2008-08-15 12:46 ` Chris Mason
2008-08-15 13:45 ` Theodore Tso
2008-08-15 17:52 ` Chris Mason
2008-08-15 19:59 ` Theodore Tso
2008-08-15 20:37 ` Chris Mason
2008-08-16 18:10 ` Chris Mason
2008-08-16 19:27 ` Theodore Tso
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=1218762627.15342.447.camel@think.oraclecorp.com \
--to=chris.mason@oracle.com \
--cc=andi@firstfloor.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.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;
as well as URLs for NNTP newsgroup(s).