From: David Nellans <david@nellans.org>
To: "Yuyang (Alex) Wang" <yyalex.wang@gmail.com>,
Carl Zwanzig <cpz@coraid.com>
Cc: Jens Axboe <axboe@kernel.dk>,
"fio@vger.kernel.org" <fio@vger.kernel.org>
Subject: Re: multiple block devices question
Date: Thu, 03 Jul 2014 12:45:46 -0500 [thread overview]
Message-ID: <53B596CA.9010407@nellans.org> (raw)
In-Reply-To: <CANyhEAuEDLvwdShA4gXoP_6_sHdEs-b7PSGymp6=H_5Bms349g@mail.gmail.com>
On 07/03/2014 12:28 PM, Yuyang (Alex) Wang wrote:
> Carl,
>
> Specifying them as separate jobs will do what I expect. However, in
> this case, I am seeking to know how much performance and how many
> devices can a __single__ FIO process can drive. If my above
> configuration is correct, then, for some reason, the single process
> doesn't increase with more devices at its disposal, not as I have seen
> from another benchmark tool - which is puzzling. I am curious to
> understand why.
>
> Best,
>
> A.
If you want to benchmark fio throughput or the block layer, not your
actual raid array,
then use a ramdisk. There are lots of flash devices out there now which
will push far
more than 1.4GB/s from a single device, rest assured fio isn't your
limitation here.
1.4 GB/s with 1M block sizes isn't even 2k IOPS. fio pushes 500k IOPS
through the block layer
without issue, its not your limiting factor.
next prev parent reply other threads:[~2014-07-03 17:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-02 19:42 multiple block devices question Yuyang (Alex) Wang
2014-07-02 19:50 ` Jens Axboe
2014-07-02 20:36 ` Yuyang (Alex) Wang
2014-07-02 23:38 ` Carl Zwanzig
2014-07-03 17:28 ` Yuyang (Alex) Wang
2014-07-03 17:45 ` David Nellans [this message]
2014-07-03 17:52 ` Yuyang (Alex) Wang
2014-07-03 18:12 ` Jeff Moyer
2014-07-03 18:21 ` Hinson, Roger
2014-07-03 18:31 ` Yuyang (Alex) Wang
2014-07-03 18:22 ` Yuyang (Alex) Wang
2014-07-03 18:39 ` Jens Axboe
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=53B596CA.9010407@nellans.org \
--to=david@nellans.org \
--cc=axboe@kernel.dk \
--cc=cpz@coraid.com \
--cc=fio@vger.kernel.org \
--cc=yyalex.wang@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.