From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu,
Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>,
Ferruh Yigit <ferruh.yigit@xilinx.com>
Subject: |SUCCESS| [GIT MASTER] abd2470902891c08fc7e407eaee17087bb7fb0d5
Date: Tue, 20 Sep 2022 21:01:49 +0000 (UTC) [thread overview]
Message-ID: <20220920210149.DFD58600A9@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 3085 bytes --]
_Performance Testing PASS_
Branch: dpdk-next-net
abd2470902891c08fc7e407eaee17087bb7fb0d5 --> performance testing pass
Test environment and result as below:
Ubuntu 20.04
Kernel: 4.15.0-generic
Compiler: gcc 7.4
NIC: Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/4
Detail performance results:
+----------+-------------+---------+------------+------------------------------+
| num_cpus | num_threads | txd/rxd | frame_size | throughput difference from |
| | | | | expected |
+==========+=============+=========+============+==============================+
| 1 | 2 | 512 | 64 | -2.5% |
+----------+-------------+---------+------------+------------------------------+
| 1 | 2 | 2048 | 64 | 0.4% |
+----------+-------------+---------+------------+------------------------------+
| 1 | 1 | 512 | 64 | 1.4% |
+----------+-------------+---------+------------+------------------------------+
| 1 | 1 | 2048 | 64 | -0.7% |
+----------+-------------+---------+------------+------------------------------+
Ubuntu 20.04
Kernel: 4.15.0-generic
Compiler: gcc 7.4
NIC: Intel Corporation Ethernet Converged Network Adapter 82599ES 10000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/6
Detail performance results:
+----------+-------------+---------+------------+------------------------------+
| num_cpus | num_threads | txd/rxd | frame_size | throughput difference from |
| | | | | expected |
+==========+=============+=========+============+==============================+
| 1 | 2 | 128 | 64 | 0.1% |
+----------+-------------+---------+------------+------------------------------+
| 1 | 2 | 512 | 64 | 0.0% |
+----------+-------------+---------+------------+------------------------------+
| 1 | 2 | 2048 | 64 | 0.3% |
+----------+-------------+---------+------------+------------------------------+
| 1 | 1 | 128 | 64 | -1.2% |
+----------+-------------+---------+------------+------------------------------+
| 1 | 1 | 512 | 64 | -0.3% |
+----------+-------------+---------+------------+------------------------------+
| 1 | 1 | 2048 | 64 | 0.2% |
+----------+-------------+---------+------------+------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/21394/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2022-09-20 21:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-20 21:01 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-09-20 20:44 dpdklab
2022-09-20 20:01 dpdklab
2022-09-20 19:49 dpdklab
2022-09-20 19:46 dpdklab
2022-09-20 18:47 dpdklab
2022-09-20 18:41 dpdklab
2022-09-20 18:30 dpdklab
2022-09-20 18:29 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=20220920210149.DFD58600A9@dpdk-ubuntu.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=ferruh.yigit@xilinx.com \
--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).