From: Olivier Doucet <webmaster@ajeux.com>
To: Hugo Mills <hugo@carfax.org.uk>,
Olivier Doucet <webmaster@ajeux.com>,
linux-btrfs@vger.kernel.org
Subject: Re: BTRFS Benchmarking
Date: Sat, 5 May 2012 01:15:39 +0200 [thread overview]
Message-ID: <CAPPqfY2aQO_y_TcFwUHUtJEOxZ6QP3XCPk5c86SUMpF31HwHCg@mail.gmail.com> (raw)
In-Reply-To: <20120504223905.GH9860@carfax.org.uk>
Hi,
I uploaded the PDF on Dropbox that does not require login
https://www.dropbox.com/s/5i8l0kmdutxj6pb/sysbench-sas3t-btrfs1.pdf
> =A0 Can you tell us what the unit of the Y-axis is? Is it MB/s or IOP=
s
> or time for a fixed amount data or... ?
Unit is MB/s ;
=46or each test, I gather speed every second.
So for a particular test, there is 60 dots (for example, speed for
BTRFS on 1 thread, blocksize=3D512b, sequential read).
As 60 dots are not easy to read, I created second pages with one
aggregated value as 95 percentile.
Sequential read results seems heavily altered by Linux pagecache. I
wondered what would be the exact methodology to disable this
optimization.
But all FS were run in the exact same behaviour (bash scripted with
umount / mount after each session).
I provided access to the bash script I used and R script to create nice=
PDF.
=46eel free to give me any feedback on how I could get results more acc=
urate.
https://github.com/odoucet/fs-benchs
> =A0 For example, in the seqwr/512 test, is btrfs doing really well at
> small numbers of threads, getting steadily worse, or is it doing
> really badly, and improves hugely as the number of threads goes up?
It is doing badly but improves when number of threads goes up.
I'll improve my benchmark results by adding self-explainable legends.
I will be happy to discuss my methodology if you think something is
wrong.
Olivier
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2012-05-04 23:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-04 16:03 BTRFS Benchmarking Olivier Doucet
2012-05-04 16:07 ` Josef Bacik
2012-05-04 22:23 ` cwillu
2012-05-07 18:42 ` Olivier Doucet
2012-05-07 19:06 ` Josef Bacik
2012-05-04 22:39 ` Hugo Mills
2012-05-04 23:15 ` Olivier Doucet [this message]
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=CAPPqfY2aQO_y_TcFwUHUtJEOxZ6QP3XCPk5c86SUMpF31HwHCg@mail.gmail.com \
--to=webmaster@ajeux.com \
--cc=hugo@carfax.org.uk \
--cc=linux-btrfs@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).