From: keith.busch@intel.com (Keith Busch)
Subject: NVMe scalability issue
Date: Tue, 2 Jun 2015 03:30:36 +0000 (UTC) [thread overview]
Message-ID: <alpine.LNX.2.00.1506020325260.15930@localhost.lm.intel.com> (raw)
In-Reply-To: <CAF1ivSZCiWjrJQWckr2cTrfHEjS99ULz0HH94XP+wW3L3Jwttg@mail.gmail.com>
On Mon, 1 Jun 2015, Ming Lin wrote:
> On Mon, Jun 1, 2015@4:02 PM, Keith Busch <keith.busch@intel.com> wrote:
>> There was a demo at SC'14 with a heck of a lot more NVMe drives than that,
>> and performance scaled quite linearly. Are your devices sharing PCI-e lanes?
>
> Is there a way to check it via, for example, /sys?
# lspci -tv
>> You could try setting "cpus_allowed" on each job to the CPU's on the
>> socket local to the nvme device. That should get a measurable improvement,
>> and if your irq's are appropriately affinitized.
>
> How to know which socket is local to which nvme device?
# cat /sys/class/nvme/nvme<#>/device/numa_node
next prev parent reply other threads:[~2015-06-02 3:30 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 [this message]
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
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=alpine.LNX.2.00.1506020325260.15930@localhost.lm.intel.com \
--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 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.