From: dpdklab@iol.unh.edu
To: Ali Alnubani <alialnu@nvidia.com>, Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu, Xueming Li <xuemingl@nvidia.com>,
Christian Ehrhardt <christian.ehrhardt@canonical.com>,
Kevin Traynor <ktraynor@redhat.com>,
Luca Boccassi <bluca@debian.org>
Subject: |SUCCESS| [GIT MASTER] 9bb15a3d0f9e33a6887ce6c0985108a2e4e0b14b
Date: Tue, 05 Dec 2023 12:12:17 -0800 (PST) [thread overview]
Message-ID: <656f8421.170a0220.a9df0.4444SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Performance Testing PASS_
Branch: 21.11-staging
9bb15a3d0f9e33a6887ce6c0985108a2e4e0b14b --> performance testing pass
Test environment and result as below:
Ubuntu 22.04
Kernel: 5.15.0-78-generic
Compiler: gcc 11.4.0
NIC: Mellanox ConnectX-5 100000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/6
Detail performance results:
+------------+---------+----------+-------------+------------------------------+
| frame_size | txd/rxd | num_cpus | num_threads | throughput difference from |
| | | | | expected |
+============+=========+==========+=============+==============================+
| 64 | 256 | 1 | 1 | 0.2% |
+------------+---------+----------+-------------+------------------------------+
| 128 | 256 | 1 | 1 | -0.2% |
+------------+---------+----------+-------------+------------------------------+
| 1024 | 256 | 1 | 1 | 0.1% |
+------------+---------+----------+-------------+------------------------------+
| 256 | 256 | 1 | 1 | -0.0% |
+------------+---------+----------+-------------+------------------------------+
| 1518 | 256 | 1 | 1 | -0.0% |
+------------+---------+----------+-------------+------------------------------+
| 512 | 256 | 1 | 1 | 0.3% |
+------------+---------+----------+-------------+------------------------------+
Ubuntu 22.04
Kernel: 5.15.0-78-generic
Compiler: gcc 11.4.0
NIC: Mellanox ConnectX-6 Lx 25000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/6
Detail performance results:
+------------+---------+----------+-------------+------------------------------+
| frame_size | txd/rxd | num_cpus | num_threads | throughput difference from |
| | | | | expected |
+============+=========+==========+=============+==============================+
| 64 | 256 | 1 | 1 | -0.1% |
+------------+---------+----------+-------------+------------------------------+
| 128 | 256 | 1 | 1 | 0.1% |
+------------+---------+----------+-------------+------------------------------+
| 1024 | 256 | 1 | 1 | 0.0% |
+------------+---------+----------+-------------+------------------------------+
| 256 | 256 | 1 | 1 | 0.1% |
+------------+---------+----------+-------------+------------------------------+
| 1518 | 256 | 1 | 1 | -0.1% |
+------------+---------+----------+-------------+------------------------------+
| 512 | 256 | 1 | 1 | -0.3% |
+------------+---------+----------+-------------+------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/27222/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-12-05 20:12 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-05 20:12 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-12-05 21:44 dpdklab
2023-12-05 21:35 dpdklab
2023-12-05 21:31 dpdklab
2023-12-05 20:48 dpdklab
2023-12-05 20:47 dpdklab
2023-12-05 20:43 dpdklab
2023-12-05 20:39 dpdklab
2023-12-05 20:37 dpdklab
2023-12-05 20:25 dpdklab
2023-12-05 20:20 dpdklab
2023-12-05 20:19 dpdklab
2023-12-05 20:19 dpdklab
2023-12-05 20:19 dpdklab
2023-12-05 20:18 dpdklab
2023-12-05 20:18 dpdklab
2023-12-05 20:17 dpdklab
2023-12-05 20:16 dpdklab
2023-12-05 20:16 dpdklab
2023-12-05 20:16 dpdklab
2023-12-05 20:15 dpdklab
2023-12-05 20:15 dpdklab
2023-12-05 20:15 dpdklab
2023-12-05 20:14 dpdklab
2023-12-05 20:13 dpdklab
2023-12-05 20:13 dpdklab
2023-12-05 20:13 dpdklab
2023-12-05 20:12 dpdklab
2023-12-05 20:11 dpdklab
2023-12-05 20:11 dpdklab
2023-12-05 20:11 dpdklab
2023-12-05 20:10 dpdklab
2023-12-05 20:10 dpdklab
2023-12-05 20:10 dpdklab
2023-12-05 20:08 dpdklab
2023-12-05 20:08 dpdklab
2023-12-05 20:08 dpdklab
2023-12-05 20:04 dpdklab
2023-12-05 20:04 dpdklab
2023-12-05 20:04 dpdklab
2023-12-05 20:03 dpdklab
2023-12-05 20:03 dpdklab
2023-12-05 20:02 dpdklab
2023-12-05 20:02 dpdklab
2023-12-05 20:02 dpdklab
2023-12-05 20:02 dpdklab
2023-12-05 20:02 dpdklab
2023-12-05 19:17 dpdklab
2023-12-05 19:15 dpdklab
2023-12-05 19:14 dpdklab
2023-12-05 19:14 dpdklab
2023-12-05 19:13 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=656f8421.170a0220.a9df0.4444SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=alialnu@nvidia.com \
--cc=bluca@debian.org \
--cc=christian.ehrhardt@canonical.com \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=ktraynor@redhat.com \
--cc=test-report@dpdk.org \
--cc=xuemingl@nvidia.com \
/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).