DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Hanoch Haim (hhaim)" <hhaim@cisco.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Cc: "Ido Barnea (ibarnea)" <ibarnea@cisco.com>,
	"Hanoch Haim (hhaim)" <hhaim@cisco.com>
Subject: [dpdk-dev]  DPDK 17.02 RC-3 performance degradation of ~10%
Date: Tue, 14 Feb 2017 11:44:38 +0000	[thread overview]
Message-ID: <e346870a62dc4a1baddca67b54880e12@XCH-RTP-017.cisco.com> (raw)

Hi,

We (trex traffic generator project) upgrade DPDK version from 16.07 to 17.02arc-3 and we experienced a performance degradation on the following NICS:

XL710  : 10-15%
ixgbe   :  8% in one case
mlx5    : 8% 2 case
X710    :  no impact (same driver as XL710)
VIC       : no impact

It might be related to DPDK infra change as it affects more than one driver (maybe mbuf?).
Wanted to know if this is expected before investing more into this. The Y axis numbers in all the following charts (from Grafana) are MPPS/core which means how many cycles per packet the CPU invest. Bigger MPPS/core means less CPU cycles to send packet.

Labeles:

trex-08 (XL710)
trex-09 (X710)
trex-07 (mlx5)
kiwi02 (ixgbe)

Grafanna charts can be seen here: (we can't share pointers to Grafanna)
https://snag.gy/wGYp3c.jpg

More information on the tests and setups can be found in this document
https://trex-tgn.cisco.com/trex/doc/trex_analytics.html


link to the project
https://github.com/cisco-system-traffic-generator/trex-core

Thanks,
Hanoh

             reply	other threads:[~2017-02-14 11:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-14 11:44 Hanoch Haim (hhaim) [this message]
2017-02-14 12:19 ` Mcnamara, John
2017-02-14 12:31   ` Hanoch Haim (hhaim)
2017-02-14 13:04   ` Thomas Monjalon
2017-02-14 13:28     ` De Lara Guarch, Pablo
2017-02-14 13:38       ` De Lara Guarch, Pablo
2017-02-15 12:35     ` Hanoch Haim (hhaim)
2017-06-21 21:24 Gudimetla, Leela Sankar
2017-06-21 22:06 Gudimetla, Leela Sankar

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=e346870a62dc4a1baddca67b54880e12@XCH-RTP-017.cisco.com \
    --to=hhaim@cisco.com \
    --cc=dev@dpdk.org \
    --cc=ibarnea@cisco.com \
    /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).