From: "Jörn Engel" <joern@logfs.org>
To: Dave Chinner <david@fromorbit.com>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: Filesystem benchmarks on reasonably fast hardware
Date: Tue, 19 Jul 2011 09:36:33 +0200 [thread overview]
Message-ID: <20110719073633.GN1437@logfs.org> (raw)
In-Reply-To: <20110719024138.GJ30254@dastard>
On Tue, 19 July 2011 12:41:38 +1000, Dave Chinner wrote:
> On Mon, Jul 18, 2011 at 01:40:36PM +0200, Jörn Engel wrote:
> > On Mon, 18 July 2011 20:57:49 +1000, Dave Chinner wrote:
> > > On Mon, Jul 18, 2011 at 09:53:39AM +0200, Jörn Engel wrote:
> > > > On Mon, 18 July 2011 09:32:52 +1000, Dave Chinner wrote:
> > > > > On Sun, Jul 17, 2011 at 06:05:01PM +0200, Jörn Engel wrote:
> > >
> > > > > > xfs:
> > > > > > ====
> > > > > > seqrd 1 2 4 8 16 32 64 128
> > > > > > 16384 4698 4424 4397 4402 4394 4398 4642 4679
> > > > > > 8192 6234 5827 5797 5801 5795 6114 5793 5812
> > > > > > 4096 9100 8835 8882 8896 8874 8890 8910 8906
> > > > > > 2048 14922 14391 14259 14248 14264 14264 14269 14273
> > > > > > 1024 23853 22690 22329 22362 22338 22277 22240 22301
> > > > > > 512 37353 33990 33292 33332 33306 33296 33224 33271
>
> > seqrd 1 2 4 8 16 32 64 128
> > 16384 4542 8311 15738 28955 38273 36644 38530 38527
> > 8192 6000 10413 19208 33878 65927 76906 77083 77102
> > 4096 8931 14971 24794 44223 83512 144867 147581 150702
> > 2048 14375 23489 34364 56887 103053 192662 307167 309222
> > 1024 21647 36022 49649 77163 132886 243296 421389 497581
> > 512 31832 61257 79545 108782 176341 303836 517814 584741
>
> > What bothers me a bit is that the single-threaded numbers took such a
> > noticeable hit...
>
> Is it reproducable? I did notice quite a bit of run-to-run variation
> in the numbers I ran. For single threaded numbers, they appear to be
> in the order of +/-100 ops @ 16k block size.
Ime the numbers are stable within about 10%. And given that out of
six measurements every single one is a regression, I would feel
confident to bet a beverage without further measurements. Regression
is 3.4%, 3.9%, 1.9%, 3.8%, 10% and 17% respectively, so the effect
appears to be more visible with smaller block numbers as well.
Jörn
--
Schrödinger's cat is <BLINK>not</BLINK> dead.
-- Illiad
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-07-19 7:36 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-17 16:05 Filesystem benchmarks on reasonably fast hardware Jörn Engel
2011-07-17 23:32 ` Dave Chinner
[not found] ` <20110718075339.GB1437@logfs.org>
2011-07-18 10:57 ` Dave Chinner
2011-07-18 11:40 ` Jörn Engel
2011-07-19 2:41 ` Dave Chinner
2011-07-19 7:36 ` Jörn Engel [this message]
2011-07-19 9:23 ` srimugunthan dhandapani
2011-07-21 19:05 ` Jörn Engel
2011-07-19 10:15 ` Dave Chinner
2011-07-18 14:34 ` Jörn Engel
[not found] ` <20110718103956.GE1437@logfs.org>
2011-07-18 11:10 ` Dave Chinner
2011-07-18 12:07 ` Ted Ts'o
2011-07-18 12:42 ` Jörn Engel
2011-07-25 15:18 ` Ted Ts'o
2011-07-25 18:20 ` Jörn Engel
2011-07-25 21:18 ` Ted Ts'o
2011-07-26 14:57 ` Ted Ts'o
2011-07-27 3:39 ` Yongqiang Yang
2011-07-19 13:19 ` Dave Chinner
2011-07-21 10:42 ` Jörn Engel
2011-07-22 18:51 ` Jörn Engel
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=20110719073633.GN1437@logfs.org \
--to=joern@logfs.org \
--cc=david@fromorbit.com \
--cc=linux-fsdevel@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).