From: Walker, Benjamin <benjamin.walker at intel.com>
To: spdk@lists.01.org
Subject: Re: [SPDK] Performance
Date: Tue, 06 Dec 2016 16:58:04 +0000 [thread overview]
Message-ID: <1481043483.4630.51.camel@intel.com> (raw)
In-Reply-To: 3E90D03A-FA74-4C9F-96E0-0E77A32BA29C@intel.com
[-- Attachment #1: Type: text/plain, Size: 2585 bytes --]
On Tue, 2016-12-06 at 16:35 +0000, Harris, James R wrote:
>
> > On Dec 6, 2016, at 5:49 AM, Kumaraparameshwaran Rathnavel <krath(a)cloudsimple
> > .com> wrote:
> >
> > The setup is the default setup of NVMf target with Direct attached
> > Subsystem. The FIO plugin was at the target side and the IOPS from SPDK was
> > found to be around 2.5K and the IOPS from kernel was found to be 100k.
>
>
> Hi Param,
>
> Can you check the AcceptorPollRate setting in your configuration file? There
> was a recent fix to the default value for this parameter. You should set it
> to at least 10000 (10ms).
>
> https://github.com/spdk/spdk/commit/5f3761cf7ec50cf03183203dc50657a9f2a18908
>
> Thanks,
Just to reinforce here - this is the solution. We saw this internally a few
weeks ago. Increasing the AcceptorPollRate to at least 10ms (you can go as much
as 1 second if you want, but the performance benefit decreases the larger you
make it), or moving the accceptor to a different core using the AcceptorCore
option will fix the problem.
>
> -Jim
>
> >
> > Regards,
> > Param.
> > > On 06-Dec-2016, at 5:57 PM, Andrey Kuzmin <andrey.v.kuzmin(a)gmail.com>
> > > wrote:
> > >
> > >
> > >
> > > On Tue, Dec 6, 2016, 15:24 Kumaraparameshwaran Rathnavel <krath(a)cloudsimpl
> > > e.com> wrote:
> > > > Hi All,
> > > >
> > > > Is there any benchmarking done to prove that SPDK is better than the
> > > > Kernel driver?
> > > >
> > > > We did run the sample driver provided from the SPDK and compared with
> > > > the kernel interface and found that SPDK is very slow. We did run FIO.
> > > >
> > >
> > > It's worth publishing your setup and results first.
> > >
> > > Regards,
> > > Andrey
> > > >
> > > > Can you describe the setup for the performance measurement between
> > > > Kernel and SPDK driver.
> > > >
> > > > Regards,
> > > > Param.
> > > > _______________________________________________
> > > > SPDK mailing list
> > > > SPDK(a)lists.01.org
> > > > https://lists.01.org/mailman/listinfo/spdk
> > > >
> > > --
> > > Regards,
> > > Andrey
> > > _______________________________________________
> > > SPDK mailing list
> > > SPDK(a)lists.01.org
> > > https://lists.01.org/mailman/listinfo/spdk
> >
> > _______________________________________________
> > SPDK mailing list
> > SPDK(a)lists.01.org
> > https://lists.01.org/mailman/listinfo/spdk
>
> _______________________________________________
> SPDK mailing list
> SPDK(a)lists.01.org
> https://lists.01.org/mailman/listinfo/spdk
next reply other threads:[~2016-12-06 16:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-06 16:58 Walker, Benjamin [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-01-18 23:41 [SPDK] Performance Walker, Benjamin
2016-12-07 1:22 Yang, Ziye
2016-12-06 16:35 Harris, James R
2016-12-06 13:20 Andrey Kuzmin
2016-12-06 13:08 Kumaraparameshwaran Rathnavel
2016-12-06 13:05 Andrey Kuzmin
2016-12-06 12:57 Kumaraparameshwaran Rathnavel
2016-12-06 12:54 Andrey Kuzmin
2016-12-06 12:49 Kumaraparameshwaran Rathnavel
2016-12-06 12:27 Andrey Kuzmin
2016-12-06 12:24 Kumaraparameshwaran Rathnavel
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=1481043483.4630.51.camel@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