From: dpdklab@iol.unh.edu
To: Ali Alnubani <alialnu@mellanox.com>, Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: [dpdk-test-report] |SUCCESS| pw49173 [PATCH] eal: fix runtime dir cleanup in noshconf mode
Date: Thu, 20 Dec 2018 04:40:22 -0800 (PST) [thread overview]
Message-ID: <5c1b8db6.1c69fb81.8c2f7.8812SMTPIN_ADDED_MISSING@mx.google.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3823 bytes --]
Test-Label: mellanox-Performance-Testing
Test-Status: SUCCESS
http://dpdk.org/patch/49173
_Performance Testing PASS_
Submitter: Burakov, Anatoly <anatoly.burakov@intel.com>
Date: Thursday, December 20 2018 11:11:48
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:7a838c8798a93fc4b0eb305c4c7d61da54875a14
49173 --> performance testing pass
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.147 |
+------------+---------+-------------------------------------+
| 128 | 256 | 0.475 |
+------------+---------+-------------------------------------+
| 256 | 256 | -0.005 |
+------------+---------+-------------------------------------+
| 512 | 256 | -0.049 |
+------------+---------+-------------------------------------+
| 1024 | 256 | -0.001 |
+------------+---------+-------------------------------------+
| 1518 | 256 | -0.002 |
+------------+---------+-------------------------------------+
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/6
Detail performance results:
+------------+---------+-------------------------------------+
| frame_size | txd/rxd | throughput difference from expected |
+============+=========+=====================================+
| 64 | 256 | 0.157 |
+------------+---------+-------------------------------------+
| 128 | 256 | 0.079 |
+------------+---------+-------------------------------------+
| 256 | 256 | 0.294 |
+------------+---------+-------------------------------------+
| 512 | 256 | -0.006 |
+------------+---------+-------------------------------------+
| 1024 | 256 | 0.003 |
+------------+---------+-------------------------------------+
| 1518 | 256 | 0.059 |
+------------+---------+-------------------------------------+
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.027 |
+------------+---------+-------------------------------------+
| 128 | 256 | 0.031 |
+------------+---------+-------------------------------------+
| 256 | 256 | 0.106 |
+------------+---------+-------------------------------------+
| 512 | 256 | -0.002 |
+------------+---------+-------------------------------------+
| 1024 | 256 | 0 |
+------------+---------+-------------------------------------+
| 1518 | 256 | -0.010 |
+------------+---------+-------------------------------------+
UNH-IOL DPDK Performance Test Lab
next reply other threads:[~2018-12-20 12:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-20 12:40 dpdklab [this message]
2018-12-20 12:40 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=5c1b8db6.1c69fb81.8c2f7.8812SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=alialnu@mellanox.com \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=test-report@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).