From: Sepehr Nazary <sepehr.nazary@googlemail.com>
To: users@dpdk.org
Subject: [dpdk-users] multi core performance problem
Date: Mon, 4 Jul 2016 14:33:45 +0430 [thread overview]
Message-ID: <CAHtRHyDPhVtW1q9D7N=LgNCV2w26uaK0cv8tD+k1uVZQ=vvSkg@mail.gmail.com> (raw)
Hi
I run dpdk multi_process (symetric_mp) example and see this result:
NumberOfCore Throughput
1 9986
2 9987
3 9808
4 9988
5 9645
6 9171
7 9030
8 8517
9 8537
10 8415
11 7832
12 7985
13 7569
14 7285
15 7624
16 6994
I run pktgen with range on and packet size is 64 byte.
I sure RSS works correctly and packets are distributed uniformly between
cores. Packet drops is 0, as well.
Why performance decrease ??
configuration :
dpdk-2.2.0, pktgen 3.0.0
NIC model : 82599ES 10-Gigabit
CPU model : Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz
Linux version 3.16.0-4-amd64
Two NUMA Node:
socket 0 : 16G RAM , 18 CORE , 2 NIC ,run DPDK symetric_mp example
socket 1 : 16G RAM , 18 CORE , 2 NIC ,run Pktgen (range on)
next reply other threads:[~2016-07-04 10:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-04 10:03 Sepehr Nazary [this message]
2016-07-04 17:34 ` Muhammad Zain-ul-Abideen
2016-07-04 17:40 ` Masoud Moshref Javadi
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='CAHtRHyDPhVtW1q9D7N=LgNCV2w26uaK0cv8tD+k1uVZQ=vvSkg@mail.gmail.com' \
--to=sepehr.nazary@googlemail.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).