From: Chris Mason <chris.mason@oracle.com>
To: Ric Wheeler <rwheeler@redhat.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: billion file testing of btrfs
Date: Mon, 16 Aug 2010 08:37:35 -0400 [thread overview]
Message-ID: <20100816123735.GV3315@think> (raw)
In-Reply-To: <4C692F24.5000208@redhat.com>
On Mon, Aug 16, 2010 at 08:29:24AM -0400, Ric Wheeler wrote:
>
> I decided to try btrfs on F13 (2.6.33.6-147.2.4.fc13.x86_64 kernel)
> with the following fs_mark command and a 1.5 TB Seagate S-ATA disk:
>
> # fs_mark -s 0 -S 0 -D 1000 -n 1000000 -L 1000 -d /test/ -l btrfs_log.txt
>
> btrfs starts off at a fantastic rate - roughly 3-4 times the speed of ext4:
>
[ log ]
>
> I will fill this and get some plots, etc to do relative performance
> & then wanted to try the current RC kernel just to refresh.
Thanks Ric, I think this is related to the perf problem delalloc
flushing performance bug. I'll nail it down shortly.
-chris
next prev parent reply other threads:[~2010-08-16 12:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-16 12:29 billion file testing of btrfs Ric Wheeler
2010-08-16 12:37 ` Chris Mason [this message]
2010-08-16 13:10 ` Ric Wheeler
2010-08-19 0:37 ` Chris Mason
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=20100816123735.GV3315@think \
--to=chris.mason@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=rwheeler@redhat.com \
/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).