DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Hanoch Haim (hhaim)" <hhaim@cisco.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] net/i40e: Significant performance degradation relative to DPDK 17.02 with TRex use-cases
Date: Fri, 24 Nov 2017 11:36:36 +0000	[thread overview]
Message-ID: <77795f7a98ec48b29ea1a95ce241e85a@XCH-RTP-017.cisco.com> (raw)

Hi All,
Significant performance degradation observed with DPDK 17.11
The Scenario is with TRex traffic generator  (https://github.com/cisco-system-traffic-generator/trex-core)


1.       Stateless mode, 64B packet stream (multi-core/single core)

DPDK 17.02 - 37-39MPPS/core
DPDK 17.11 - 33.5MPPS/core

~12% degradation


2.       Stateless mode, Field Engine  (Multi-core)


DPDK 17.02 - 14MPPS/core
DPDK 17.11 -11.8MPPS/core

~15% degradation


3.       Only DPDK was replaced

4.       Is this expected?

The full report can be found here:
https://trex-tgn.cisco.com/trex/doc/trex_analytics.html



*         Mellanox CX-5 (mlx5) shows significant improvement

*         Ixgbe shows improvement

Thanks,
Hanoh

             reply	other threads:[~2017-11-24 11:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-24 11:36 Hanoch Haim (hhaim) [this message]
2017-11-24 16:03 ` Alejandro Lucero

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=77795f7a98ec48b29ea1a95ce241e85a@XCH-RTP-017.cisco.com \
    --to=hhaim@cisco.com \
    --cc=dev@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).