From: Marco Stornelli <marco.stornelli@gmail.com>
To: Jan Kara <jack@suse.cz>
Cc: Dave Chinner <david@fromorbit.com>,
xfs@oss.sgi.com, linux-fsdevel@vger.kernel.org
Subject: Re: Some baseline tests on new hardware (was Re: [PATCH] xfs: optimise CIL insertion during transaction commit [RFC])
Date: Mon, 08 Jul 2013 17:22:43 +0200 [thread overview]
Message-ID: <51DAD943.6050703@gmail.com> (raw)
In-Reply-To: <20130708135953.GF5988@quack.suse.cz>
Il 08/07/2013 15:59, Jan Kara ha scritto:
> On Mon 08-07-13 22:44:53, Dave Chinner wrote:
> <snipped some nice XFS results ;)>
>> So, lets look at ext4 vs btrfs vs XFS at 16-way (this is on the
>> 3.10-cil kernel I've been testing XFS on):
>>
>> create walk unlink
>> time(s) rate time(s) time(s)
>> xfs 222 266k+-32k 170 295
>> ext4 978 54k+- 2k 325 2053
>> btrfs 1223 47k+- 8k 366 12000(*)
>>
>> (*) Estimate based on a removal rate of 18.5 minutes for the first
>> 4.8 million inodes.
>>
>> Basically, neither btrfs or ext4 have any concurrency scaling to
>> demonstrate, and unlinks on btrfs a just plain woeful.
> Thanks for posting the numbers. There isn't anyone seriously testing ext4
> SMP scalability AFAIK so it's not surprising it sucks.
Funny, if I well remember Google guys switched android from yaffs2 to
ext4 due to its superiority on SMP :)
Marco
next prev parent reply other threads:[~2013-07-08 15:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1372657476-9241-1-git-send-email-david@fromorbit.com>
2013-07-08 12:44 ` Some baseline tests on new hardware (was Re: [PATCH] xfs: optimise CIL insertion during transaction commit [RFC]) Dave Chinner
2013-07-08 13:59 ` Jan Kara
2013-07-08 15:22 ` Marco Stornelli [this message]
2013-07-08 15:38 ` Jan Kara
2013-07-09 0:15 ` Dave Chinner
2013-07-09 0:56 ` Theodore Ts'o
2013-07-09 0:43 ` Zheng Liu
2013-07-09 1:23 ` Dave Chinner
2013-07-09 1:15 ` Chris Mason
2013-07-09 1:26 ` Dave Chinner
2013-07-09 1:54 ` [BULK] " Chris Mason
2013-07-09 8:26 ` Dave Chinner
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=51DAD943.6050703@gmail.com \
--to=marco.stornelli@gmail.com \
--cc=david@fromorbit.com \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=xfs@oss.sgi.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).