linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Chris Mason <chris.mason@oracle.com>,
	Freek Dijkstra <Freek.Dijkstra@sara.nl>,
	linux-btrfs@vger.kernel.org
Subject: Re: Poor read performance on high-end server
Date: Fri, 06 Aug 2010 13:55:21 +0200	[thread overview]
Message-ID: <4C5BF829.3020200@kernel.dk> (raw)
In-Reply-To: <20100805145138.GJ29846@think>

On 2010-08-05 16:51, Chris Mason wrote:
> And then we need to setup a fio job file that hammers on all the ssds at
> once.  I'd have it use adio/dio and talk directly to the drives.  I'd do
> something like this for the fio job file, but Jens Axboe is cc'd and he
> might make another suggestion on the job file.  I'd do something like
> this in a file named ssd.fio
> 
> [global]
> size=32g
> direct=1
> iodepth=8

iodepth=8 will have no effect if you don't also set a different IO
engine, otherwise you would be using read(2) to fetch the data. So add
ioengine=libaio to take advantage of a higher queue depth as well.

Also, I didn't see Chris mention this, but if you have a newer intel box
you can use hw accellerated crc32c instead. For some reason my test box
always loads crc32c and not crc32c-intel, so I need to do that manually.
That helps a lot with higher transfer rates. You can check support for
hw crc32c by checking for the 'sse4_2' flag in /proc/cpuinfo.

-- 
Jens Axboe


  parent reply	other threads:[~2010-08-06 11: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 [this message]
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
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=4C5BF829.3020200@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=Freek.Dijkstra@sara.nl \
    --cc=chris.mason@oracle.com \
    --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).