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] fe4b05502dd6db1061e8c926418277c33f57199d
Date: Thu, 30 Mar 2023 05:05:50 +0000 (UTC) [thread overview]
Message-ID: <20230330050550.7DA5860123@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
_Performance Testing PASS_
Branch: tags/v21.11
fe4b05502dd6db1061e8c926418277c33f57199d --> performance testing pass
Test environment and result as below:
Ubuntu 22.04
Kernel: 5.15.0-39-generic
Compiler: gcc gcc (Ubuntu 11.2.0-19ubuntu1) 11.2.0
NIC: Broadcom Inc. and subsidiaries BCM57414 NetXtreme-E 10Gb/25Gb RDMA Ethernet Controller 16d7 25 Mbps
Target: x86_64-native-linuxapp-gcc
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.1% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 2048 | 1 | 1 | 0.0% |
+------------+---------+----------+-------------+------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/24098/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-03-30 5:05 UTC|newest]
Thread overview: 98+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-30 5:05 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-03-30 5:43 dpdklab
2023-03-30 5:36 dpdklab
2023-03-30 5:20 dpdklab
2023-03-30 5:18 dpdklab
2023-03-30 5:17 dpdklab
2023-03-30 5:17 dpdklab
2023-03-30 5:13 dpdklab
2023-03-30 5:01 dpdklab
2023-03-30 5:01 dpdklab
2023-03-30 5:00 dpdklab
2023-03-30 4:59 dpdklab
2023-03-30 4:55 dpdklab
2023-03-30 4:54 dpdklab
2023-03-30 4:53 dpdklab
2023-03-30 4:52 dpdklab
2023-03-29 11:35 dpdklab
2023-03-29 7:48 dpdklab
2023-03-29 6:37 dpdklab
2023-03-29 6:27 dpdklab
2023-03-29 6:15 dpdklab
2023-03-29 5:26 dpdklab
2023-03-29 5:22 dpdklab
2023-03-29 5:22 dpdklab
2023-03-29 5:17 dpdklab
2023-03-29 5:13 dpdklab
2023-03-29 5:12 dpdklab
2023-03-29 5:08 dpdklab
2023-03-29 5:07 dpdklab
2023-03-29 5:05 dpdklab
2023-03-29 5:04 dpdklab
2023-03-29 4:59 dpdklab
2023-03-29 4:57 dpdklab
2023-03-28 17:37 dpdklab
2023-03-28 15:36 dpdklab
2023-03-28 13:58 dpdklab
2023-03-28 10:18 dpdklab
2023-03-28 9:58 dpdklab
2023-03-28 7:40 dpdklab
2023-03-28 6:27 dpdklab
2023-03-28 6:14 dpdklab
2023-03-28 6:01 dpdklab
2023-03-28 5:45 dpdklab
2023-03-28 5:31 dpdklab
2023-03-28 5:25 dpdklab
2023-03-28 5:19 dpdklab
2023-03-28 5:15 dpdklab
2023-03-28 5:08 dpdklab
2023-03-28 5:06 dpdklab
2023-03-28 4:59 dpdklab
2023-03-28 4:52 dpdklab
2023-03-26 3:51 dpdklab
2023-03-25 6:47 dpdklab
2023-03-25 4:04 dpdklab
2023-03-24 18:41 dpdklab
2023-03-24 16:50 dpdklab
2023-03-24 16:33 dpdklab
2023-03-24 14:29 dpdklab
2023-03-24 7:47 dpdklab
2023-03-24 5:52 dpdklab
2023-03-24 5:40 dpdklab
2023-03-24 5:26 dpdklab
2023-03-24 5:23 dpdklab
2023-03-24 5:20 dpdklab
2023-03-24 5:15 dpdklab
2023-03-24 5:12 dpdklab
2023-03-24 5:04 dpdklab
2023-03-24 5:03 dpdklab
2023-03-24 4:58 dpdklab
2023-03-24 4:51 dpdklab
2023-03-23 12:19 dpdklab
2023-03-23 11:56 dpdklab
2023-03-23 7:41 dpdklab
2023-03-23 5:51 dpdklab
2023-03-23 5:40 dpdklab
2023-03-23 5:39 dpdklab
2023-03-23 5:27 dpdklab
2023-03-23 5:24 dpdklab
2023-03-23 5:21 dpdklab
2023-03-23 5:13 dpdklab
2023-03-23 5:06 dpdklab
2023-03-23 5:06 dpdklab
2023-03-23 5:03 dpdklab
2023-03-23 4:59 dpdklab
2023-03-23 4:53 dpdklab
2023-03-23 4:32 dpdklab
2023-03-23 3:23 dpdklab
2023-03-23 3:20 dpdklab
2023-03-23 3:18 dpdklab
2023-03-23 3:14 dpdklab
2023-03-23 3:10 dpdklab
2023-03-23 3:08 dpdklab
2023-03-23 3:04 dpdklab
2023-03-23 3:02 dpdklab
2023-03-23 3:01 dpdklab
2023-03-23 2:58 dpdklab
2023-03-23 2:56 dpdklab
2023-03-23 2:51 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=20230330050550.7DA5860123@dpdk-ubuntu.dpdklab.iol.unh.edu \
--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).