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] 802f39367e08d2916cd21f7b6a34703bc8672a38
Date: Wed, 20 Nov 2024 03:54:59 -0800 (PST) [thread overview]
Message-ID: <673dce13.050a0220.2c8865.382bSMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Performance Testing PASS_
Branch: tags/v22.11
802f39367e08d2916cd21f7b6a34703bc8672a38 --> performance testing pass
Upstream job id: Template-DTS-Pipeline#197765
Test environment and result as below:
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.1% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 512 | 1 | 1 | -0.6% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 2048 | 1 | 1 | -0.1% |
+------------+---------+----------+-------------+------------------------------+
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.0% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 2048 | 1 | 1 | 0.0% |
+------------+---------+----------+-------------+------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/31653/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-11-20 11:55 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-20 11:54 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-11-20 13:16 dpdklab
2024-11-20 12:55 dpdklab
2024-11-20 12:40 dpdklab
2024-11-20 12:20 dpdklab
2024-11-20 11:59 dpdklab
2024-11-20 11:36 dpdklab
2024-11-20 10:31 dpdklab
2024-11-20 9:55 dpdklab
2024-11-20 9:00 dpdklab
2024-11-20 7:43 dpdklab
2024-11-20 7:08 dpdklab
2024-11-20 7:06 dpdklab
2024-11-20 7:02 dpdklab
2024-11-20 6:12 dpdklab
2024-11-20 3:57 dpdklab
2024-11-20 2:24 dpdklab
2024-11-20 0:41 dpdklab
2024-11-20 0:08 dpdklab
2024-11-19 23:15 dpdklab
2024-11-19 23:12 dpdklab
2024-11-19 22:19 dpdklab
2024-11-19 21:55 dpdklab
2024-11-19 21:53 dpdklab
2024-11-19 21:52 dpdklab
2024-11-19 21:43 dpdklab
2024-11-19 21:42 dpdklab
2024-11-19 21:36 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=673dce13.050a0220.2c8865.382bSMTPIN_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).