From: "Hanoch Haim (hhaim)" <hhaim@cisco.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>,
"Mcnamara, John" <john.mcnamara@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"Ido Barnea (ibarnea)" <ibarnea@cisco.com>
Subject: Re: [dpdk-dev] DPDK 17.02 RC-3 performance degradation of ~10%
Date: Wed, 15 Feb 2017 12:35:56 +0000 [thread overview]
Message-ID: <09de078b09d44c47b78bd5234462505e@XCH-RTP-017.cisco.com> (raw)
In-Reply-To: <1793839.gziRDArGs7@xps13>
Hi Thomas and John,
We found that the performance degradation is not related to DPDK 17.02 for Intel XL710/ixgbe. Now It is back to normal. The fix was to add a one unrelated line to a specific file. This probably changed the instructions trace. This line is not related to DP or CP. (We still don't fully understand that).
Mlx5 small degradation wasn't solved yet.
Thanks,
Hanoh
-----Original Message-----
From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com]
Sent: Tuesday, February 14, 2017 3:05 PM
To: Hanoch Haim (hhaim)
Cc: dev@dpdk.org; Mcnamara, John; Ido Barnea (ibarnea)
Subject: Re: [dpdk-dev] DPDK 17.02 RC-3 performance degradation of ~10%
2017-02-14 12:19, Mcnamara, John:
> From: Hanoch Haim (hhaim)
> > 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:
[...]
>
> Could you do a git-bisect to identify the change that caused this?
+1 for the bisect.
Please could you try to isolate the change causing the regression?
next prev parent reply other threads:[~2017-02-15 12:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-14 11:44 Hanoch Haim (hhaim)
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) [this message]
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=09de078b09d44c47b78bd5234462505e@XCH-RTP-017.cisco.com \
--to=hhaim@cisco.com \
--cc=dev@dpdk.org \
--cc=ibarnea@cisco.com \
--cc=john.mcnamara@intel.com \
--cc=thomas.monjalon@6wind.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).