From: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
To: Dave Chinner <david@fromorbit.com>
Cc: linux-fsdevel@vger.kernel.org, tux3@tux3.org,
Daniel Phillips <daniel.raymond.phillips@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: Tux3 Report: Faster than tmpfs, what?
Date: Tue, 14 May 2013 16:59:29 +0900 [thread overview]
Message-ID: <87mwrydmam.fsf@devron.myhome.or.jp> (raw)
In-Reply-To: <20130514063438.GF29466@dastard> (Dave Chinner's message of "Tue, 14 May 2013 16:34:38 +1000")
Dave Chinner <david@fromorbit.com> writes:
>> Right. Because tux3 is not implementing fsync() yet. So, I did
>>
>> grep -v Flush /usr/share/dbench/client.txt > client2.txt
>>
>> Why is it important for comparing?
>
> Because nobody could reproduce your results without working that
> out. You didn't disclose that you'd made these changes, and that
> makes it extremely misleading as to what the results mean. Given the
> headline-grab nature of it, it's deceptive at best.
>
> I don't care how fast tux3 is - I care about being able to reproduce
> other people's results. Hence if you are going to report benchmark
> results comparing filesystems then you need to tell everyone exactly
> what you've tweaked and why, from the hardware all the way up to the
> benchmark config.
Thanks for adivce.
--
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
next prev parent reply other threads:[~2013-05-14 7:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-07 23:24 Tux3 Report: Faster than tmpfs, what? Daniel Phillips
2013-05-10 4:50 ` Dave Chinner
2013-05-10 5:06 ` Christian Stroetmann
2013-05-10 5:47 ` OGAWA Hirofumi
2013-05-14 6:34 ` Dave Chinner
2013-05-14 7:59 ` OGAWA Hirofumi [this message]
2013-05-11 6:12 ` Daniel Phillips
2013-05-11 18:35 ` james northrup
2013-05-12 4:39 ` Daniel Phillips
2013-05-11 21:26 ` Theodore Ts'o
2013-05-12 4:28 ` Daniel Phillips
2013-05-13 23:22 ` Daniel Phillips
[not found] ` <35557711-A88D-4226-B3C6-3787573F5403@dilger.ca>
2013-05-14 6:25 ` Daniel Phillips
2013-05-15 17:10 ` Andreas Dilger
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=87mwrydmam.fsf@devron.myhome.or.jp \
--to=hirofumi@mail.parknet.co.jp \
--cc=daniel.raymond.phillips@gmail.com \
--cc=david@fromorbit.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tux3@tux3.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