From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>, Patrick Robb <probb@iol.unh.edu>
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: |FAILURE| [GIT MASTER] 9784db2c5af1eecd02fc21132b59b5b266039b87
Date: Sat, 15 Nov 2025 21:15:38 -0800 (PST) [thread overview]
Message-ID: <69195dfa.050a0220.1839b6.9916SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Performance Testing issues_
Branch: tags/v22.11
9784db2c5af1eecd02fc21132b59b5b266039b87 --> performance testing issues
Upstream job id: Template-DTS-Pipeline#255124
Test environment and result as below:
Ubuntu 22.04
Kernel: 5.15
Compiler: gcc gcc (Ubuntu 11.4.0-1ubuntu1~22.04.2) 11.4.0
NIC: Arm Broadcom Inc. brcm_57414 25000 Mbps
Fail/Total: 0/1
Detail performance results:
The measurement deltas are not ready yet! Please check back later.
Ubuntu 22.04
Kernel: 5.15
Compiler: gcc 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: 1/3
Failed cases list:
- DTS https://dpdklab.iol.unh.edu/results/testcases/1/
Detail performance results:
+------------+---------+----------+-------------+------------------------------+
| frame_size | txd/rxd | num_cpus | num_threads | throughput difference from |
| | | | | expected |
+============+=========+==========+=============+==============================+
| 64 | 128 | 1 | 1 | -7.5% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 512 | 1 | 1 | -6.0% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 2048 | 1 | 1 | -5.1% |
+------------+---------+----------+-------------+------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/35614/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2025-11-16 5:15 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-16 5:15 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-11-16 9:41 dpdklab
2025-11-16 6:55 dpdklab
2025-11-16 6:47 dpdklab
2025-11-16 6:04 dpdklab
2025-11-16 5:56 dpdklab
2025-11-16 5:56 dpdklab
2025-11-16 5:11 dpdklab
2025-11-15 11:28 dpdklab
2025-11-15 11:22 dpdklab
2025-11-15 7:27 dpdklab
2025-11-15 5:17 dpdklab
2025-11-15 2:31 dpdklab
2025-11-14 6:17 dpdklab
2025-11-14 6:11 dpdklab
2025-11-14 6:08 dpdklab
2025-11-14 5:14 dpdklab
2025-11-14 1:57 dpdklab
2025-11-14 1:49 dpdklab
2025-11-13 13:35 dpdklab
2025-11-13 13:22 dpdklab
2025-11-13 5:55 dpdklab
2025-11-13 1:33 dpdklab
2025-11-13 1:13 dpdklab
2025-11-12 6:05 dpdklab
2025-11-12 5:13 dpdklab
2025-11-11 6:12 dpdklab
2025-11-11 5:08 dpdklab
2025-11-10 7:33 dpdklab
2025-11-10 7:01 dpdklab
2025-11-09 6:24 dpdklab
2025-11-09 6:07 dpdklab
2025-11-09 6:03 dpdklab
2025-11-09 5:48 dpdklab
2025-11-09 5:48 dpdklab
2025-11-09 5:47 dpdklab
2025-11-09 5:38 dpdklab
2025-11-08 12:01 dpdklab
2025-11-08 6:56 dpdklab
2025-11-08 6:25 dpdklab
2025-11-07 22:10 dpdklab
2025-11-07 6:58 dpdklab
2025-11-07 6:44 dpdklab
2025-11-07 6:41 dpdklab
2025-11-07 5:55 dpdklab
2025-11-07 5:42 dpdklab
2025-11-07 5:15 dpdklab
2025-11-06 11:36 dpdklab
2025-11-06 6:40 dpdklab
2025-11-06 6:02 dpdklab
2025-11-06 5:35 dpdklab
2025-11-06 5:35 dpdklab
2025-11-06 5:18 dpdklab
2025-11-06 5:17 dpdklab
2025-11-05 6:27 dpdklab
2025-11-05 5:22 dpdklab
2025-11-05 5:18 dpdklab
2025-11-05 5:09 dpdklab
2025-11-04 8:33 dpdklab
2025-11-04 8:09 dpdklab
2025-11-04 6:58 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=69195dfa.050a0220.1839b6.9916SMTPIN_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=probb@iol.unh.edu \
--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).