From: Jens Axboe <jaxboe@fusionio.com>
To: Josh Aune <luken@omner.org>
Cc: , john smith <whalajam@yahoo.com>,
"fio@vger.kernel.org" <fio@vger.kernel.org>
Subject: Re: uneven IOPS among HD
Date: Mon, 28 Feb 2011 08:07:45 -0500 [thread overview]
Message-ID: <4D6B9E21.70705@fusionio.com> (raw)
In-Reply-To: <AANLkTi=nLVRq6=AFvhsoWX_ThjHrxaqkw=kcyLUQrr13@mail.gmail.com>
On 2011-02-26 15:31, Josh Aune wrote:
> On Sunday, February 20, 2011, Jens Axboe <jaxboe@fusionio.com> wrote:
>> On 2011-02-17 03:14, john smith wrote:
>>> I have a couple of questions:
>>>
>>> 1) if it is normal (and if so, why) that while running a number of identical jobs (e.g 4), each bound to a different CPU (cpu_allowed=i) and each performing sequential (bs=512) reads on (e.g. 4) different HD, fio reports IOPS numbers that are highly unbalanced among HD with one HD reporting more than 7x of the IOPS of the minimum IOPS HD.
>>> Different runs may show most of the IOPS on a different HD, so it's not that one HD is faster.
>>>
>>> Here are some possibly interesting parameters:
>>>
>>> ioengine=libaio
>>> iodepth=32
>>> direct=1
>>
>> There should be very little variance between runs, and between jobs.
>> Each are separate threads/processes, so most of the variance you will
>> see will be due to system "artifacts". So I'd suggest you look there. If
>> you don't pin to specific CPUs, do you see smaller or larger
>> differences?
>>
>> Are you doing random or sequential IO? Could also be timing differences
>> in submission and dispatch from the IO scheduler.
>
> Is hyper threading enabled? Could be running some of the jobs on the
> same CPU core.
>
> Does it track to different sockets?
No, the replay doesn't factor in CPU placement of the apps submitting
IO.
--
Jens Axboe
prev parent reply other threads:[~2011-02-28 13:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-17 2:14 uneven IOPS among HD john smith
2011-02-20 19:11 ` Jens Axboe
2011-02-26 20:31 ` Josh Aune
2011-02-28 13:07 ` Jens Axboe [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=4D6B9E21.70705@fusionio.com \
--to=jaxboe@fusionio.com \
--cc=fio@vger.kernel.org \
--cc=luken@omner.org \
--cc=whalajam@yahoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox