From: dpdklab@iol.unh.edu
To: Erez Scop <erezsc@mellanox.com>,
Thomas Monjalon <thomas@monjalon.net>,
Ali Alnubani <alialnu@mellanox.com>,
Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: [dpdk-test-report] |FAILURE| pw56419 [PATCH] [v3] net/ice: fix flow validation fail
Date: Sun, 14 Jul 2019 23:45:30 -0400 (EDT) [thread overview]
Message-ID: <20190715034530.DB617DF59F@noxus.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 3194 bytes --]
Test-Label: mellanox-Performance-Testing
Test-Status: FAILURE
http://dpdk.org/patch/56419
_Performance Testing issues_
Submitter: Yang, Qiming <qiming.yang@intel.com>
Date: Monday, July 15 2019 02:23:56
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:8de5ede7b61d9b1af40485755cfcd2d525a6c816
56419 --> performance testing fail
Test environment and result as below:
Ubuntu 16.04
Kernel: 4.4.0-109-generic
GCC: 5.4.0-6ubuntu1~16.04.6
NIC: Mellanox ConnectX-4 Lx 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/6
Detail performance results:
+------------+---------+-------------------------------------+
| frame_size | txd/rxd | throughput difference from expected |
+============+=========+=====================================+
| 64 | 256 | 0.578 |
+------------+---------+-------------------------------------+
| 128 | 256 | -0.387 |
+------------+---------+-------------------------------------+
| 256 | 256 | -0.067 |
+------------+---------+-------------------------------------+
| 512 | 256 | 0.011 |
+------------+---------+-------------------------------------+
| 1024 | 256 | -0.002 |
+------------+---------+-------------------------------------+
| 1518 | 256 | -0.017 |
+------------+---------+-------------------------------------+
Ubuntu 16.04
Kernel: 4.4.0-109-generic
GCC: 5.4.0-6ubuntu1~16.04.6
NIC: Mellanox ConnectX-5 100000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/0
Detail performance results:
There were no deltas reported. There may have been an issue with the test harness. If logs are available, download them from the ci website for more information.
Ubuntu 16.04
Kernel: 4.4.0-109-generic
GCC: 5.4.0-6ubuntu1~16.04.6
NIC: Mellanox ConnectX-4 Lx 25000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/6
Detail performance results:
+------------+---------+-------------------------------------+
| frame_size | txd/rxd | throughput difference from expected |
+============+=========+=====================================+
| 64 | 256 | 0.454 |
+------------+---------+-------------------------------------+
| 128 | 256 | -0.188 |
+------------+---------+-------------------------------------+
| 256 | 256 | 0.040 |
+------------+---------+-------------------------------------+
| 512 | 256 | 0.006 |
+------------+---------+-------------------------------------+
| 1024 | 256 | 0.002 |
+------------+---------+-------------------------------------+
| 1518 | 256 | 0.004 |
+------------+---------+-------------------------------------+
https://lab.dpdk.org/results/dashboard/patchsets/6587/
UNH-IOL DPDK Performance Test Lab
To manage your email subscriptions visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
reply other threads:[~2019-07-15 3:45 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=20190715034530.DB617DF59F@noxus.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=alialnu@mellanox.com \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=erezsc@mellanox.com \
--cc=test-report@dpdk.org \
--cc=thomas@monjalon.net \
/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).