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] 4401486b5e30d43a134f80f9802f60b5f43e74a8
Date: Sat, 12 Apr 2025 22:02:32 -0700 (PDT) [thread overview]
Message-ID: <67fb4568.050a0220.3cbf22.5dd3SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Performance Testing PASS_
Branch: tags/v22.11
4401486b5e30d43a134f80f9802f60b5f43e74a8 --> performance testing pass
Upstream job id: Template-DTS-Pipeline#221408
Test environment and result as below:
Ubuntu 24.04
Kernel: 6.8.0-45-generic
Compiler: gcc 13.2.0
NIC: NVIDIA Mellanox ConnectX-7 100000 Mbps
Fail/Total: 0/6
Detail performance results:
+------------+---------+----------+-------------+------------------------------+
| frame_size | txd/rxd | num_cpus | num_threads | throughput difference from |
| | | | | expected |
+============+=========+==========+=============+==============================+
| 64 | 1024 | 1 | 1 | -0.3% |
+------------+---------+----------+-------------+------------------------------+
| 128 | 1024 | 1 | 1 | 0.0% |
+------------+---------+----------+-------------+------------------------------+
| 256 | 1024 | 1 | 1 | -0.3% |
+------------+---------+----------+-------------+------------------------------+
| 512 | 1024 | 1 | 1 | 0.1% |
+------------+---------+----------+-------------+------------------------------+
| 1024 | 1024 | 1 | 1 | 0.2% |
+------------+---------+----------+-------------+------------------------------+
| 1518 | 1024 | 1 | 1 | -0.1% |
+------------+---------+----------+-------------+------------------------------+
Ubuntu 24.04
Kernel: 6.8.0-45-generic
Compiler: gcc 13.2.0
NIC: Mellanox ConnectX-6 Lx 25000 Mbps
Fail/Total: 0/6
Detail performance results:
+------------+---------+----------+-------------+------------------------------+
| frame_size | txd/rxd | num_cpus | num_threads | throughput difference from |
| | | | | expected |
+============+=========+==========+=============+==============================+
| 64 | 1024 | 1 | 1 | 0.0% |
+------------+---------+----------+-------------+------------------------------+
| 128 | 1024 | 1 | 1 | 0.1% |
+------------+---------+----------+-------------+------------------------------+
| 256 | 1024 | 1 | 1 | -0.1% |
+------------+---------+----------+-------------+------------------------------+
| 512 | 1024 | 1 | 1 | -0.1% |
+------------+---------+----------+-------------+------------------------------+
| 1024 | 1024 | 1 | 1 | 0.2% |
+------------+---------+----------+-------------+------------------------------+
| 1518 | 1024 | 1 | 1 | -0.2% |
+------------+---------+----------+-------------+------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/33241/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2025-04-13 5:02 UTC|newest]
Thread overview: 67+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-13 5:02 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-04-15 22:02 dpdklab
2025-04-15 8:04 dpdklab
2025-04-15 7:00 dpdklab
2025-04-15 6:41 dpdklab
2025-04-15 6:09 dpdklab
2025-04-15 5:44 dpdklab
2025-04-15 5:39 dpdklab
2025-04-15 5:29 dpdklab
2025-04-15 5:19 dpdklab
2025-04-14 7:46 dpdklab
2025-04-14 7:20 dpdklab
2025-04-14 6:47 dpdklab
2025-04-14 6:27 dpdklab
2025-04-14 6:24 dpdklab
2025-04-14 6:20 dpdklab
2025-04-14 6:08 dpdklab
2025-04-14 6:06 dpdklab
2025-04-14 5:39 dpdklab
2025-04-14 5:29 dpdklab
2025-04-14 4:39 dpdklab
2025-04-13 7:23 dpdklab
2025-04-13 7:16 dpdklab
2025-04-13 6:37 dpdklab
2025-04-13 6:30 dpdklab
2025-04-13 6:13 dpdklab
2025-04-13 5:49 dpdklab
2025-04-13 5:40 dpdklab
2025-04-13 5:28 dpdklab
2025-04-13 5:08 dpdklab
2025-04-13 4:49 dpdklab
2025-04-13 4:39 dpdklab
2025-04-12 8:13 dpdklab
2025-04-12 7:48 dpdklab
2025-04-12 6:17 dpdklab
2025-04-12 6:13 dpdklab
2025-04-12 5:47 dpdklab
2025-04-12 5:45 dpdklab
2025-04-12 5:40 dpdklab
2025-04-12 5:23 dpdklab
2025-04-12 5:00 dpdklab
2025-04-12 4:39 dpdklab
2025-04-12 4:29 dpdklab
2025-04-11 22:27 dpdklab
2025-04-11 21:41 dpdklab
2025-04-11 9:14 dpdklab
2025-04-11 7:49 dpdklab
2025-04-11 7:47 dpdklab
2025-04-11 7:25 dpdklab
2025-04-11 6:17 dpdklab
2025-04-11 5:52 dpdklab
2025-04-11 5:44 dpdklab
2025-04-11 5:32 dpdklab
2025-04-11 5:12 dpdklab
2025-04-11 5:05 dpdklab
2025-04-11 4:49 dpdklab
2025-04-10 9:40 dpdklab
2025-04-10 8:52 dpdklab
2025-04-10 8:01 dpdklab
2025-04-10 7:03 dpdklab
2025-04-10 6:39 dpdklab
2025-04-10 6:37 dpdklab
2025-04-10 6:20 dpdklab
2025-04-10 5:43 dpdklab
2025-04-10 5:34 dpdklab
2025-04-10 5:27 dpdklab
2025-04-10 5:12 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=67fb4568.050a0220.3cbf22.5dd3SMTPIN_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).