From: dpdklab@iol.unh.edu
To: 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] 03f2ed63a5f4e4b57365e358b49095ef4a82cf7d
Date: Fri, 11 Apr 2025 23:23:54 -0700 (PDT) [thread overview]
Message-ID: <67fa06fa.050a0220.294dc6.3247SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Performance Testing PASS_
Branch: tags/v24.11
03f2ed63a5f4e4b57365e358b49095ef4a82cf7d --> performance testing pass
Upstream job id: Template-DTS-Pipeline#221359
Test environment and result as below:
Ubuntu 22.04 ARM
Kernel: 5.15.83+
Compiler: gcc 11.4.0
NIC: Arm Broadcom Inc. brcm_57414 25000 Mbps
Fail/Total: 0/2
Detail performance results:
+------------+---------+----------+-------------+------------------------------+
| frame_size | txd/rxd | num_cpus | num_threads | throughput difference from |
| | | | | expected |
+============+=========+==========+=============+==============================+
| 64 | 512 | 1 | 1 | -0.3% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 2048 | 1 | 1 | -0.1% |
+------------+---------+----------+-------------+------------------------------+
Ubuntu 22.04
Kernel: 5.15.0-100-generic
Compiler: gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
NIC: Broadcom Inc. and subsidiaries BCM57414 NetXtreme-E 10Gb/25Gb RDMA Ethernet Controller 16d7 25 Mbps
Fail/Total: 0/3
Detail performance results:
+------------+---------+----------+-------------+------------------------------+
| frame_size | txd/rxd | num_cpus | num_threads | throughput difference from |
| | | | | expected |
+============+=========+==========+=============+==============================+
| 64 | 128 | 1 | 1 | -0.2% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 512 | 1 | 1 | -0.7% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 2048 | 1 | 1 | -0.9% |
+------------+---------+----------+-------------+------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/33236/
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-12 6:23 UTC|newest]
Thread overview: 219+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-12 6:23 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-04-13 7:39 dpdklab
2025-04-13 6:37 dpdklab
2025-04-13 5:57 dpdklab
2025-04-13 5:53 dpdklab
2025-04-13 5:43 dpdklab
2025-04-13 5:30 dpdklab
2025-04-13 4:48 dpdklab
2025-04-13 4:43 dpdklab
2025-04-13 4:37 dpdklab
2025-04-13 4:35 dpdklab
2025-04-13 4:35 dpdklab
2025-04-13 4:33 dpdklab
2025-04-13 4:27 dpdklab
2025-04-13 4:21 dpdklab
2025-04-12 7:31 dpdklab
2025-04-12 7:30 dpdklab
2025-04-12 6:49 dpdklab
2025-04-12 6:41 dpdklab
2025-04-12 6:41 dpdklab
2025-04-12 6:08 dpdklab
2025-04-12 6:03 dpdklab
2025-04-12 4:44 dpdklab
2025-04-12 4:43 dpdklab
2025-04-12 4:36 dpdklab
2025-04-12 4:35 dpdklab
2025-04-12 4:33 dpdklab
2025-04-12 4:29 dpdklab
2025-04-12 4:25 dpdklab
2025-04-12 4:19 dpdklab
2025-04-12 4:14 dpdklab
2025-04-11 22:18 dpdklab
2025-04-11 21:23 dpdklab
2025-04-11 9:07 dpdklab
2025-04-11 7:37 dpdklab
2025-04-11 6:01 dpdklab
2025-04-11 5:47 dpdklab
2025-04-11 5:37 dpdklab
2025-04-11 5:37 dpdklab
2025-04-11 5:07 dpdklab
2025-04-11 5:01 dpdklab
2025-04-11 4:52 dpdklab
2025-04-11 4:41 dpdklab
2025-04-11 4:37 dpdklab
2025-04-11 4:37 dpdklab
2025-04-11 4:35 dpdklab
2025-04-11 4:23 dpdklab
2025-04-10 8:00 dpdklab
2025-04-10 7:12 dpdklab
2025-04-10 6:44 dpdklab
2025-04-10 5:54 dpdklab
2025-04-10 5:36 dpdklab
2025-04-10 5:19 dpdklab
2025-04-10 5:02 dpdklab
2025-04-10 4:47 dpdklab
2025-04-10 4:35 dpdklab
2025-04-10 4:33 dpdklab
2025-04-10 4:33 dpdklab
2025-04-10 4:27 dpdklab
2025-04-10 4:19 dpdklab
2025-04-09 6:56 dpdklab
2025-04-09 6:04 dpdklab
2025-04-09 5:50 dpdklab
2025-04-09 5:40 dpdklab
2025-04-09 5:30 dpdklab
2025-04-09 5:29 dpdklab
2025-04-09 5:28 dpdklab
2025-04-09 5:26 dpdklab
2025-04-09 5:23 dpdklab
2025-04-09 5:14 dpdklab
2025-04-07 19:21 dpdklab
2025-04-07 19:03 dpdklab
2025-04-07 18:54 dpdklab
2025-04-07 7:09 dpdklab
2025-04-07 6:41 dpdklab
2025-04-07 6:11 dpdklab
2025-04-07 5:46 dpdklab
2025-04-07 5:18 dpdklab
2025-04-07 5:14 dpdklab
2025-04-07 5:14 dpdklab
2025-04-07 5:03 dpdklab
2025-04-07 5:00 dpdklab
2025-04-07 4:51 dpdklab
2025-04-07 4:38 dpdklab
2025-04-07 4:33 dpdklab
2025-04-07 4:31 dpdklab
2025-04-06 6:20 dpdklab
2025-04-06 6:19 dpdklab
2025-04-06 5:48 dpdklab
2025-04-06 5:44 dpdklab
2025-04-06 5:35 dpdklab
2025-04-06 5:27 dpdklab
2025-04-06 5:27 dpdklab
2025-04-06 4:40 dpdklab
2025-04-06 4:38 dpdklab
2025-04-06 4:34 dpdklab
2025-04-06 4:26 dpdklab
2025-04-06 4:22 dpdklab
2025-04-06 4:17 dpdklab
2025-04-06 4:17 dpdklab
2025-04-05 8:35 dpdklab
2025-04-05 8:19 dpdklab
2025-04-05 7:59 dpdklab
2025-04-05 7:56 dpdklab
2025-04-05 6:41 dpdklab
2025-04-05 6:20 dpdklab
2025-04-05 6:17 dpdklab
2025-04-05 6:09 dpdklab
2025-04-05 6:02 dpdklab
2025-04-05 5:47 dpdklab
2025-04-05 5:32 dpdklab
2025-04-05 5:27 dpdklab
2025-04-05 4:48 dpdklab
2025-04-05 4:36 dpdklab
2025-04-04 17:31 dpdklab
2025-04-04 16:21 dpdklab
2025-04-04 8:33 dpdklab
2025-04-04 7:46 dpdklab
2025-04-04 6:53 dpdklab
2025-04-04 6:45 dpdklab
2025-04-04 6:34 dpdklab
2025-04-04 6:17 dpdklab
2025-04-04 6:15 dpdklab
2025-04-04 5:57 dpdklab
2025-04-04 4:48 dpdklab
2025-04-04 4:39 dpdklab
2025-04-04 4:38 dpdklab
2025-04-04 4:32 dpdklab
2025-04-04 4:26 dpdklab
2025-04-03 23:07 dpdklab
2025-04-03 22:44 dpdklab
2025-04-03 13:27 dpdklab
2025-04-03 9:32 dpdklab
2025-04-03 9:19 dpdklab
2025-04-03 9:00 dpdklab
2025-04-03 9:00 dpdklab
2025-04-03 8:09 dpdklab
2025-04-03 6:32 dpdklab
2025-04-03 5:59 dpdklab
2025-04-03 5:50 dpdklab
2025-04-03 5:35 dpdklab
2025-04-03 5:31 dpdklab
2025-04-03 5:23 dpdklab
2025-04-03 5:05 dpdklab
2025-04-02 8:21 dpdklab
2025-04-02 7:20 dpdklab
2025-04-02 6:37 dpdklab
2025-04-02 6:15 dpdklab
2025-04-02 5:57 dpdklab
2025-04-02 5:18 dpdklab
2025-04-02 5:17 dpdklab
2025-04-02 4:45 dpdklab
2025-04-02 4:38 dpdklab
2025-04-02 4:36 dpdklab
2025-04-02 4:32 dpdklab
2025-04-02 4:29 dpdklab
2025-04-02 4:23 dpdklab
2025-04-02 4:17 dpdklab
2025-04-02 4:17 dpdklab
2025-04-01 7:41 dpdklab
2025-04-01 6:35 dpdklab
2025-04-01 6:32 dpdklab
2025-04-01 6:16 dpdklab
2025-04-01 6:12 dpdklab
2025-04-01 6:02 dpdklab
2025-04-01 5:34 dpdklab
2025-04-01 5:31 dpdklab
2025-04-01 5:31 dpdklab
2025-04-01 5:28 dpdklab
2025-04-01 5:17 dpdklab
2025-04-01 4:42 dpdklab
2025-04-01 4:36 dpdklab
2025-03-31 10:07 dpdklab
2025-03-31 7:30 dpdklab
2025-03-31 6:57 dpdklab
2025-03-31 6:10 dpdklab
2025-03-31 5:55 dpdklab
2025-03-31 5:42 dpdklab
2025-03-31 5:34 dpdklab
2025-03-31 5:33 dpdklab
2025-03-31 5:17 dpdklab
2025-03-31 5:16 dpdklab
2025-03-31 5:07 dpdklab
2025-03-31 5:06 dpdklab
2025-03-31 4:52 dpdklab
2025-03-31 4:44 dpdklab
2025-03-30 7:58 dpdklab
2025-03-30 7:30 dpdklab
2025-03-30 7:27 dpdklab
2025-03-30 6:56 dpdklab
2025-03-30 6:07 dpdklab
2025-03-30 5:59 dpdklab
2025-03-30 5:30 dpdklab
2025-03-30 4:52 dpdklab
2025-03-30 4:37 dpdklab
2025-03-30 4:36 dpdklab
2025-03-30 4:32 dpdklab
2025-03-30 4:28 dpdklab
2025-03-30 4:21 dpdklab
2025-03-30 4:17 dpdklab
2025-03-30 4:17 dpdklab
2025-03-29 10:17 dpdklab
2025-03-29 8:06 dpdklab
2025-03-29 7:59 dpdklab
2025-03-29 7:43 dpdklab
2025-03-29 7:04 dpdklab
2025-03-29 6:35 dpdklab
2025-03-29 6:26 dpdklab
2025-03-29 6:14 dpdklab
2025-03-29 6:14 dpdklab
2025-03-29 5:50 dpdklab
2025-03-29 5:48 dpdklab
2025-03-29 5:35 dpdklab
2025-03-29 5:20 dpdklab
2025-03-29 5:19 dpdklab
2025-03-29 5:13 dpdklab
2025-03-29 5:13 dpdklab
2025-03-29 4:58 dpdklab
2025-03-29 4:49 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=67fa06fa.050a0220.294dc6.3247SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--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).