From: Dheeraj Dang <dheerajdang138@gmail.com>
To: users@dpdk.org
Subject: [dpdk-users] Strange Packet Loss with number of flows.
Date: Thu, 26 Sep 2019 10:10:25 +0530 [thread overview]
Message-ID: <CAJyVW49=bNG6mzpyLfeAbbfUKqiOcsiKJv34v-2U17vhBD+kew@mail.gmail.com> (raw)
Hi,
I am having a problem with packet loss and I hope you can help me out.
When we increase the number of flows, PPM value must increase. I observed
this behavior to some point, but after that PPM value reduces. Below you
find the description of application, workload, and observations.
*Application*
I have a server-client application, a single server, and single client.
Both machines are using multiple queues to send or receive packets.
*Workload*
I'm running dpdk with fixed PPS value i.e 2 Mpps.
I'm increasing the number of flows to see the impact on PPM value.
I'm changing UDP port range to generate the number of flows.
*Observations*
Target MPPS Flows PPM
2 2 100
2 100 670
2 1000 3136
2 5000 265878
2 10000 106316
*I was expecting PPM value to rise for 10K flows, but its value reduces.*
Please share your suggestions.
Regards
Dheeraj Dang
next reply other threads:[~2019-09-26 4:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-26 4:40 Dheeraj Dang [this message]
2019-09-26 5:17 ` Stephen Hemminger
2019-09-26 9:42 ` Dheeraj Dang
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='CAJyVW49=bNG6mzpyLfeAbbfUKqiOcsiKJv34v-2U17vhBD+kew@mail.gmail.com' \
--to=dheerajdang138@gmail.com \
--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).