linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chris Mason <chris.mason@oracle.com>
To: Freek Dijkstra <Freek.Dijkstra@sara.nl>
Cc: Jens Axboe <axboe@kernel.dk>, Andi Kleen <andi@firstfloor.org>,
	"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: Poor read performance on high-end server
Date: Mon, 9 Aug 2010 20:55:39 -0400	[thread overview]
Message-ID: <20100810005539.GI10525@think> (raw)
In-Reply-To: <4C601499.5040402@sara.nl>

On Mon, Aug 09, 2010 at 04:45:45PM +0200, Freek Dijkstra wrote:
> Hi all,
> 
> Thanks a lot for the great feedback from before the weekend. Since one
> of my colleagues needed the machine, I could only do the tests today.
> 
> In short: just installing 2.6.35 did make some difference, but I was
> mostly impressed with the speedup gained by the hardware acceleration of
> the crc32c_intel module.
> 
> Here is some quick data.
> 
> Reference figures:
> 16* single disk (theoretical limit):     4092 MiByte/s
> fio data layer tests (achievable limit): 3250 MiByte/s
> ZFS performance:                         2505 MiByte/s
> 
> BtrFS figures:
> IOzone on 2.6.32:                         919 MiByte/s
> fio btrfs tests on 2.6.35:               1460 MiByte/s

Was this one with O_DIRECT?

> IOzone on 2.6.35 with crc32c:            1250 MiByte/s
> IOzone on 2.6.35 with crc32c_intel:      1629 MiByte/s
> IOzone on 2.6.35, using -o nodatasum:    1955 MiByte/s
> 
> For those finding this message and want a howto: the easiest way to use
> crc32c_intel is to add the module name to /etc/modules:
>  # echo "crc32c_intel" >> /etc/modules
>  # reboot
> 
> Now the next step for us is to tune the block sizes. We only did that
> preliminary, but now that we have a good knowledge of what software to
> use, we can start tuning that in more detail.
> 
> If there is interest on this list, I'll gladly post our results here.

Definitely, please do.

-chris

  reply	other threads:[~2010-08-10  0:55 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-05 14:05 Poor read performance on high-end server Freek Dijkstra
2010-08-05 14:51 ` Chris Mason
2010-08-05 21:21   ` Freek Dijkstra
2010-08-05 22:13     ` Daniel J Blueman
2010-08-06 11:41     ` Chris Mason
2010-08-06 11:55   ` Jens Axboe
2010-08-06 11:59     ` Chris Mason
2010-08-20  4:53       ` Sander
2010-08-20 14:37         ` Chris Mason
2010-08-08  7:18     ` Andi Kleen
2010-08-08 11:04       ` Jens Axboe
2010-08-09 14:45         ` Freek Dijkstra
2010-08-10  0:55           ` Chris Mason [this message]
2010-08-05 14:54 ` Daniel J Blueman
2010-08-05 16:21 ` Mathieu Chouquet-Stringer

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=20100810005539.GI10525@think \
    --to=chris.mason@oracle.com \
    --cc=Freek.Dijkstra@sara.nl \
    --cc=andi@firstfloor.org \
    --cc=axboe@kernel.dk \
    --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).