All of lore.kernel.org
 help / color / mirror / Atom feed
From: keith.busch@intel.com (Keith Busch)
Subject: Scalability issue with multiple NVMe Devices with one core
Date: Thu, 13 Oct 2016 10:18:21 -0400	[thread overview]
Message-ID: <20161013141820.GA17823@localhost.localdomain> (raw)
In-Reply-To: <50e02652-9e54-c314-6551-cd3075ccb005@mellanox.com>

On Thu, Oct 13, 2016@08:44:37AM +0300, Roy Shterman wrote:
> scenario is when running traffic over 1 NVMe Device with 1 core I'm getting
> X IOPS and Y% core utilization.
> 
> In my perception, when adding more NVMe Devices I should see some linearity
> of the above results, but I'm getting only a small improvement in IOPS and
> still not getting 100% (or closer ) in CPU utilization.
> 
> Any suggestions?

How are you generating IO?

  reply	other threads:[~2016-10-13 14:18 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 [this message]
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
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=20161013141820.GA17823@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 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.