From: Harris, James R <james.r.harris at intel.com>
To: spdk@lists.01.org
Subject: Re: [SPDK] Number of NVMe devices per core
Date: Thu, 15 Feb 2018 14:50:38 +0000 [thread overview]
Message-ID: <89940C85-FD9D-4890-9812-47F7A0FC27A2@intel.com> (raw)
In-Reply-To: CAHK_hpK8r85mqFQ3-b97Otb5fYHOFsVURoRMKr6ZNTBB=y41jQ@mail.gmail.com
[-- Attachment #1: Type: text/plain, Size: 956 bytes --]
Hi Ernest,
The answer depends on many different factors – the IOPs limit per device, CPU core frequency, Turbo, etc. As a frame of reference, the team here at Intel has measured over 3M IO/s on a single Intel Xeon core[1].
-Jim
[1] https://www.flashmemorysummit.com/English/Collaterals/Proceedings/2016/20160809_FA12_P3_Prepalli.pdf - slide 63
From: SPDK <spdk-bounces(a)lists.01.org> on behalf of Ernest Zed <kreuzerkrieg(a)gmail.com>
Reply-To: Storage Performance Development Kit <spdk(a)lists.01.org>
Date: Thursday, February 15, 2018 at 6:46 AM
To: Storage Performance Development Kit <spdk(a)lists.01.org>
Subject: [SPDK] Number of NVMe devices per core
Hi All,
I ran 'perf' with different settings to see how to get most of NVMe disks. I see that performance degrades once cpu mask puts more than 2 devises per core. Is it OK? what is the theoretical (or empirical) limit of devices one core can handle?
Sincerely,
Ernest
[-- Attachment #2: attachment.html --]
[-- Type: text/html, Size: 4259 bytes --]
next reply other threads:[~2018-02-15 14:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-15 14:50 Harris, James R [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-02-18 12:24 [SPDK] Number of NVMe devices per core Ernest Zed
2018-02-15 18:24 Ernest Zed
2018-02-15 18:22 Ernest Zed
2018-02-15 17:55 Verma, Vishal4
2018-02-15 17:52 Verkamp, Daniel
2018-02-15 17:42 Ernest Zed
2018-02-15 16:54 Verma, Vishal4
2018-02-15 16:45 Ernest Zed
2018-02-15 16:17 Verma, Vishal4
2018-02-15 15:51 Ernest Zed
2018-02-15 15:35 Harris, James R
2018-02-15 15:26 Ernest Zed
2018-02-15 13:46 Ernest Zed
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=89940C85-FD9D-4890-9812-47F7A0FC27A2@intel.com \
--to=spdk@lists.01.org \
/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