From: Kumaraparameshwaran Rathnavel <krath at cloudsimple.com>
To: spdk@lists.01.org
Subject: Re: [SPDK] Performance
Date: Tue, 06 Dec 2016 18:27:53 +0530 [thread overview]
Message-ID: <525F4BDF-6656-47C0-968F-5176B0887995@cloudsimple.com> (raw)
In-Reply-To: CANvN+enc=f+mp=t22bW0b_urOEPx7oopi2Uni_VFJ9PYq2X7Fw@mail.gmail.com
[-- Attachment #1: Type: text/plain, Size: 2415 bytes --]
Can you briefly describe your setup if you don’t mind.
It will be of great help.
Regards,
Param.
> On 06-Dec-2016, at 6:24 PM, Andrey Kuzmin <andrey.v.kuzmin(a)gmail.com> wrote:
>
>
>
> On Tue, Dec 6, 2016, 15:49 Kumaraparameshwaran Rathnavel <krath(a)cloudsimple.com <mailto: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.
>
> Sounds like a setup issue to me. In my tests, SPDK typically matched or surpassed kernel stack in IOPS while using 2-3x less CPU.
>
> Regards,
> Andrey
>
> Regards,
> Param.
>
>> On 06-Dec-2016, at 5:57 PM, Andrey Kuzmin <andrey.v.kuzmin(a)gmail.com <mailto:andrey.v.kuzmin(a)gmail.com>> wrote:
>>
>>
>>
>> On Tue, Dec 6, 2016, 15:24 Kumaraparameshwaran Rathnavel <krath(a)cloudsimple.com <mailto:krath(a)cloudsimple.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 <mailto:SPDK(a)lists.01.org>
>> https://lists.01.org/mailman/listinfo/spdk <https://lists.01.org/mailman/listinfo/spdk>
>> --
>> Regards,
>> Andrey
>>
>> _______________________________________________
>> SPDK mailing list
>> SPDK(a)lists.01.org <mailto:SPDK(a)lists.01.org>
>> https://lists.01.org/mailman/listinfo/spdk <https://lists.01.org/mailman/listinfo/spdk>
>
> _______________________________________________
> SPDK mailing list
> SPDK(a)lists.01.org <mailto:SPDK(a)lists.01.org>
> https://lists.01.org/mailman/listinfo/spdk <https://lists.01.org/mailman/listinfo/spdk>
> --
> Regards,
> Andrey
>
> _______________________________________________
> SPDK mailing list
> SPDK(a)lists.01.org <mailto:SPDK(a)lists.01.org>
> https://lists.01.org/mailman/listinfo/spdk <https://lists.01.org/mailman/listinfo/spdk>
[-- Attachment #2: attachment.html --]
[-- Type: text/html, Size: 11664 bytes --]
next reply other threads:[~2016-12-06 12:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-06 12:57 Kumaraparameshwaran Rathnavel [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:58 Walker, Benjamin
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: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=525F4BDF-6656-47C0-968F-5176B0887995@cloudsimple.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