From: keith.busch@intel.com (Keith Busch)
Subject: Scalability issue with multiple NVMe Devices with one core
Date: Thu, 13 Oct 2016 11:07:23 -0400 [thread overview]
Message-ID: <20161013150723.GC17823@localhost.localdomain> (raw)
In-Reply-To: <2F56CFEA-4C6D-48B9-92B0-C4E74AF0B60B@mellanox.com>
On Thu, Oct 13, 2016@02:48:34PM +0000, Roy Shterman wrote:
>> And if you append "--name task_nvme1n1 --filename=/dev/nvme1n1" to this
>> command, you are not observing a
>> meaningful IOPS improvement?
>
> I appended only --filename=/dev/nvme0n1 without the new name, I'm not sure if it makes any difference but I can check.
If you don't add --name, fio isn't going to start another job, so you're
not accessing the devices in parallel and shouldn't expect an IOPS
improvement.
next prev parent reply other threads:[~2016-10-13 15:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-13 5:44 Scalability issue with multiple NVMe Devices with one core Roy Shterman
2016-10-13 14:18 ` Keith Busch
2016-10-13 14:11 ` Roy Shterman
2016-10-13 14:44 ` Keith Busch
[not found] ` <2F56CFEA-4C6D-48B9-92B0-C4E74AF0B60B@mellanox.com>
2016-10-13 15:07 ` Keith Busch [this message]
2016-10-13 14:13 ` Roy Shterman
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=20161013150723.GC17823@localhost.localdomain \
--to=keith.busch@intel.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