From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 522] Performance degradation on AWS ena driver
Date: Mon, 10 Aug 2020 08:22:25 +0000 [thread overview]
Message-ID: <bug-522-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=522
Bug ID: 522
Summary: Performance degradation on AWS ena driver
Product: DPDK
Version: 19.11
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: ethdev
Assignee: dev@dpdk.org
Reporter: tudor.cornea@gmail.com
Target Milestone: ---
Created attachment 115
--> https://bugs.dpdk.org/attachment.cgi?id=115&action=edit
AWS ena comparison between 18.11 and 19.11
Greetings,
I ran a test with DPDK 19.11 over the AWS ena driver, and seem to get lower
performance than with the previous release, 18.11
It seems that more CPU is being spent in ena_com_prepare_tx,compared to the
previous release.
I have attached a file, containing more detailed measurements
OS: Ubuntu 18
AWS Instance Type: C5.4xlarge
DPDK 19.11 + pktgen 19.12
Tx Rate: 1800 Mbits/s
18.11 + Pktgen 3.7.0
Tx Rate: 400 Mbits/s
Could somebody confirm if there is indeed a degradation between builds, and
point me to a possible fix ?
Thanks,
Tudor
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2020-08-10 8:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=bug-522-3@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--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).