From: David Nellans <david@nellans.org>
To: tech8891 <tech8891@163.com>, fio@vger.kernel.org
Subject: Re: very unstable IOPS in the same test on the same machine
Date: Thu, 02 Jan 2014 09:40:24 -0600 [thread overview]
Message-ID: <52C58868.4050800@nellans.org> (raw)
In-Reply-To: <266864ba.12fb3.1435264174a.Coremail.tech8891@163.com>
> Problem summary:
> The IOPS is very unstable since I changed the number of jobs from 2 to 4. even I changed it back, the IOPS performance also can't return back.
> # cat 1.fio
> [global]
> rw=randread
> size=128m
>
> [job1]
>
> [job2]
>
> when I run fio 1.fio, the iops is around 31k. and then I add the following 2 entries:
> [job3]
>
> [job4]
>
> The IOPS dropped to around 1k.
>
> Even I remove these 2 jobs, the IOPS still be around 1k.
>
> Only if I removed all the jobn.n.0 files, and re-run with 2 jobs setting, the IOPS can be 31k again.
> # bash blkinfo.sh /dev/sda
> Vendor : LSI
> Model : MR9260-8i
> Nr_request : 128
> rotational : 1
It looks like you're testing against a LSI megaraid SAS controller,
which presumably has magnetic drives attached. When you add more jobs
to your config its going to cause the heads on the drives (you don't say
how many you have) to thrash more as they try and interleave requests
that are going to land on different portions of the disk. So its not
unsurprising that you'll see IOPS drop off.
A lot of how and where the IOPS will drop off is going to depend on the
raid config of the drives you have attached to the controller however.
Generally speaking 31k IOPS at 128MB I/O's (which will be split into
something smaller like 1MB typically) is well beyond what you should
expect 8 HDD's to do unless you're getting lots of hits in the DRAM
buffer on the raid controller. Enterprise HDD's (even 15k ones)
generally can only sustain <= 250 random read IOPS, so even with perfect
interleaving on an 8 drive raid-0, 31k seem suspicious, 1k seems
perfectly realistic however!
next prev parent reply other threads:[~2014-01-02 15:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-02 9:58 very unstable IOPS in the same test on the same machine tech8891
2014-01-02 15:40 ` David Nellans [this message]
2014-01-02 17:04 ` Roger Sibert
2014-01-03 3:14 ` tech8891
2014-01-03 3:37 ` David Nellans
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=52C58868.4050800@nellans.org \
--to=david@nellans.org \
--cc=fio@vger.kernel.org \
--cc=tech8891@163.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