From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |PENDING| [GIT MASTER] 3d06f2c35c938a268311c3e0a57d0cd6010c3c1d
Date: Wed, 10 Jul 2024 06:46:51 -0700 (PDT) [thread overview]
Message-ID: <668e90cb.050a0220.669b0.abdfSMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Performance Testing pending_
Branch: 23.11-staging
3d06f2c35c938a268311c3e0a57d0cd6010c3c1d --> performance testing pending
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
Target: Unknown
Fail/Total: 0/3
Detail performance results:
+------------+---------+----------+-------------+------------------------------+
| frame_size | txd/rxd | num_cpus | num_threads | throughput difference from |
| | | | | expected |
+============+=========+==========+=============+==============================+
| 64 | 128 | 1 | 1 | 0.3% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 512 | 1 | 1 | -1.1% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 2048 | 1 | 1 | -0.5% |
+------------+---------+----------+-------------+------------------------------+
Ubuntu 22.04 ARM
Kernel: 5.15.83+
Compiler: gcc 11.4.0
NIC: Arm Broadcom Inc. brcm_57414 25000 Mbps
Target: Unknown
Fail/Total: 0/1
Detail performance results:
The measurement deltas are not ready yet! Please check back later.
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/29801/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-07-10 13:46 UTC|newest]
Thread overview: 74+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-10 13:46 dpdklab [this message]
2024-07-10 13:53 dpdklab
2024-07-10 13:55 dpdklab
2024-07-10 14:07 dpdklab
2024-07-10 14:08 dpdklab
2024-07-10 14:08 dpdklab
2024-07-10 14:08 dpdklab
2024-07-10 14:10 dpdklab
2024-07-10 14:10 dpdklab
2024-07-10 14:11 dpdklab
2024-07-10 14:12 dpdklab
2024-07-10 14:13 dpdklab
2024-07-10 14:14 dpdklab
2024-07-10 14:16 dpdklab
2024-07-10 14:17 dpdklab
2024-07-10 14:17 dpdklab
2024-07-10 14:17 dpdklab
2024-07-10 14:17 dpdklab
2024-07-10 14:18 dpdklab
2024-07-10 14:18 dpdklab
2024-07-10 14:18 dpdklab
2024-07-10 14:19 dpdklab
2024-07-10 14:19 dpdklab
2024-07-10 14:20 dpdklab
2024-07-10 14:20 dpdklab
2024-07-10 14:21 dpdklab
2024-07-10 14:22 dpdklab
2024-07-10 14:24 dpdklab
2024-07-10 14:24 dpdklab
2024-07-10 14:27 dpdklab
2024-07-10 14:27 dpdklab
2024-07-10 14:27 dpdklab
2024-07-10 14:28 dpdklab
2024-07-10 14:28 dpdklab
2024-07-10 14:28 dpdklab
2024-07-10 14:29 dpdklab
2024-07-10 14:30 dpdklab
2024-07-10 14:31 dpdklab
2024-07-10 14:32 dpdklab
2024-07-10 14:33 dpdklab
2024-07-10 14:33 dpdklab
2024-07-10 14:33 dpdklab
2024-07-10 14:35 dpdklab
2024-07-10 14:36 dpdklab
2024-07-10 14:37 dpdklab
2024-07-10 14:37 dpdklab
2024-07-10 14:38 dpdklab
2024-07-10 14:39 dpdklab
2024-07-10 14:40 dpdklab
2024-07-10 14:41 dpdklab
2024-07-10 14:42 dpdklab
2024-07-10 14:42 dpdklab
2024-07-10 14:46 dpdklab
2024-07-10 14:48 dpdklab
2024-07-10 14:53 dpdklab
2024-07-10 14:55 dpdklab
2024-07-10 15:01 dpdklab
2024-07-10 15:02 dpdklab
2024-07-10 15:07 dpdklab
2024-07-10 15:21 dpdklab
2024-07-10 15:22 dpdklab
2024-07-10 15:24 dpdklab
2024-07-10 15:28 dpdklab
2024-07-10 15:30 dpdklab
2024-07-10 15:33 dpdklab
2024-07-10 15:35 dpdklab
2024-07-10 15:37 dpdklab
2024-07-10 15:37 dpdklab
2024-07-10 15:40 dpdklab
2024-07-10 15:42 dpdklab
2024-07-10 15:43 dpdklab
2024-07-10 15:48 dpdklab
2024-07-10 15:56 dpdklab
2024-07-10 16:05 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=668e90cb.050a0220.669b0.abdfSMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=test-report@dpdk.org \
/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).