From: Sungho Hong <shong59@asu.edu>
To: users@dpdk.org
Subject: [dpdk-users] Bad IO-latency when sending one rte_mbuf at a time
Date: Thu, 19 Jul 2018 14:09:11 -0700 [thread overview]
Message-ID: <CAKf1RwCGF3tjA7=d8DwsaxDQmRpEL=Zq7yOfyM2Bp=GVraP6NA@mail.gmail.com> (raw)
Hello, I am testing single round-trip latency of a single message using
DPDK and POSIX.
The round-trip latency that I am talking about is that
I send one message in other words rte_mbuf *m[1] from client to server,
and the server echos back to the client .
I have tested this same thing on both POSIX and DPDK, and DPDK performance
is really bad when I do this.
for example when using POSIX
the total round-trip latency is 1275.666667 usec
while when I use DPDK
the total round-trip latency is 61322
In the past, I have only tested DPDK based on run-time on sending a bulk of
data, for example 10 Gigabyte of files, in that case, I remember that DPDK
outperforms POSIX.
I believe that I am using the DPDK in the wrong way, or missing something
very critical. the test cases that I have built can be viewed here.
https://github.com/SungHoHong2/Ceph-Experiment/tree/master/DPDK-FUSE/FUSE-2nd
Would it be possible to know how I can improve the performance of a
round-trip latency of a single message?
(Or is this not ideal for DPDK?)
Best
Sungho Hong
reply other threads:[~2018-07-19 21:09 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CAKf1RwCGF3tjA7=d8DwsaxDQmRpEL=Zq7yOfyM2Bp=GVraP6NA@mail.gmail.com' \
--to=shong59@asu.edu \
--cc=users@dpdk.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;
as well as URLs for NNTP newsgroup(s).