From: dpdklab@iol.unh.edu
To: Ali Alnubani <alialnu@mellanox.com>,
Erez Scop <erezsc@mellanox.com>,
Thomas Monjalon <thomas@monjalon.net>,
Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: [dpdk-test-report] |FAILURE| pw69757-69763 [PATCH] [1/7] common/dpaax: move internal symbols into INTERNAL section
Date: Tue, 5 May 2020 12:59:07 -0400 (EDT) [thread overview]
Message-ID: <20200505165907.4B88C65F93@noxus.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 3188 bytes --]
Test-Label: iol-mellanox-Performance
Test-Status: FAILURE
http://dpdk.org/patch/69757
_Performance Testing issues_
Submitter: Hemant Agrawal <hemant.agrawal@nxp.com>
Date: Tuesday, May 05 2020 14:08:26
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:67d376e7fe7d4e4149d3591ed94cba33206e8cd2
69757-69763 --> performance testing fail
Test environment and result as below:
Ubuntu 18.04
Kernel: 4.15.0-generic
Compiler: gcc 7.4
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 18.04
Kernel: 4.15.0-generic
Compiler: gcc 7.4
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.187 |
+------------+---------+-------------------------------------+
| 128 | 256 | -0.040 |
+------------+---------+-------------------------------------+
| 256 | 256 | -0.051 |
+------------+---------+-------------------------------------+
| 512 | 256 | 0.018 |
+------------+---------+-------------------------------------+
| 1024 | 256 | -0.004 |
+------------+---------+-------------------------------------+
| 1518 | 256 | 0 |
+------------+---------+-------------------------------------+
Ubuntu 18.04
Kernel: 4.15.0-generic
Compiler: gcc 7.4
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.532 |
+------------+---------+-------------------------------------+
| 128 | 256 | 0.112 |
+------------+---------+-------------------------------------+
| 256 | 256 | 0.029 |
+------------+---------+-------------------------------------+
| 512 | 256 | 0.003 |
+------------+---------+-------------------------------------+
| 1024 | 256 | 0.001 |
+------------+---------+-------------------------------------+
| 1518 | 256 | -0.018 |
+------------+---------+-------------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/10892/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2020-05-05 16:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-05 16:59 dpdklab [this message]
2020-05-06 8:26 dpdklab
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=20200505165907.4B88C65F93@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).