From: m@bjorling.me (Matias Bjørling)
Subject: NVMe scalability issue
Date: Tue, 02 Jun 2015 09:58:34 +0200 [thread overview]
Message-ID: <556D622A.805@bjorling.me> (raw)
In-Reply-To: <1433199171.7699.22.camel@ssi>
On 06/02/2015 12:52 AM, Ming Lin wrote:
> Hi list,
>
> [global]
> rw=randread
> bs=4k
> direct=1
> ioengine=libaio
> iodepth=64
> time_based
> runtime=60
> group_reporting
> numjobs=4
>
> [job0]
> filename=/dev/nvme0n1
>
> [job1]
> filename=/dev/nvme1n1
>
> [job2]
> filename=/dev/nvme2n1
>
> [job3]
> filename=/dev/nvme3n1
>
> [job4]
> filename=/dev/nvme4n1
>
> [job5]
> filename=/dev/nvme5n1
>
> [job6]
> filename=/dev/nvme6n1
>
> [job7]
> filename=/dev/nvme7n1
>
A wild guess, the jobs might run on a remote CPU compared to the device.
Try to affinitize the jobs so they run on the CPU with the attached device.
next prev parent reply other threads:[~2015-06-02 7:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-01 22:52 NVMe scalability issue Ming Lin
2015-06-01 23:02 ` Keith Busch
2015-06-01 23:24 ` Ming Lin
2015-06-02 3:30 ` Keith Busch
2015-06-02 17:24 ` Ming Lin
2015-06-02 18:22 ` Jens Axboe
2015-06-02 20:55 ` Ming Lin
2015-06-01 23:28 ` Azher Mughal
2015-06-02 7:58 ` Matias Bjørling [this message]
2015-06-02 19:03 ` Andrey Kuzmin
2015-06-02 19:09 ` Jens Axboe
2015-06-02 19:11 ` Andrey Kuzmin
2015-06-02 19:14 ` 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=556D622A.805@bjorling.me \
--to=m@bjorling.me \
/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