From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| [GIT MASTER] 502b07c4e0c2b250a33325d6f2fbd28d2aad5af7
Date: Thu, 30 May 2024 12:14:08 -0700 (PDT) [thread overview]
Message-ID: <6658d000.170a0220.f4fc2.0cafSMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Performance Testing PASS_
Branch: dpdk-next-net-intel
502b07c4e0c2b250a33325d6f2fbd28d2aad5af7 --> performance testing pass
Test environment and result as below:
Ubuntu 22.04
Kernel: 5.15.0-94-generic
Compiler: gcc 11.4.0
NIC: Mellanox ConnectX-6 Lx 25000 Mbps
Target: Unknown
Fail/Total: 0/6
Detail performance results:
+------------+---------+----------+-------------+------------------------------+
| frame_size | txd/rxd | num_cpus | num_threads | throughput difference from |
| | | | | expected |
+============+=========+==========+=============+==============================+
| 64 | 256 | 1 | 1 | -0.4% |
+------------+---------+----------+-------------+------------------------------+
| 128 | 256 | 1 | 1 | -0.1% |
+------------+---------+----------+-------------+------------------------------+
| 1024 | 256 | 1 | 1 | -0.1% |
+------------+---------+----------+-------------+------------------------------+
| 256 | 256 | 1 | 1 | 0.1% |
+------------+---------+----------+-------------+------------------------------+
| 1518 | 256 | 1 | 1 | 0.3% |
+------------+---------+----------+-------------+------------------------------+
| 512 | 256 | 1 | 1 | -0.4% |
+------------+---------+----------+-------------+------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/29252/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-05-30 19:14 UTC|newest]
Thread overview: 83+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-30 19:14 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-05-30 19:18 dpdklab
2024-05-30 19:14 dpdklab
2024-05-30 14:35 dpdklab
2024-05-30 12:43 dpdklab
2024-05-30 12:09 dpdklab
2024-05-30 12:02 dpdklab
2024-05-30 12:01 dpdklab
2024-05-30 11:57 dpdklab
2024-05-30 11:52 dpdklab
2024-05-30 11:46 dpdklab
2024-05-30 11:44 dpdklab
2024-05-30 11:42 dpdklab
2024-05-30 11:41 dpdklab
2024-05-30 11:39 dpdklab
2024-05-30 11:38 dpdklab
2024-05-30 11:35 dpdklab
2024-05-30 11:35 dpdklab
2024-05-30 11:35 dpdklab
2024-05-30 11:35 dpdklab
2024-05-30 11:35 dpdklab
2024-05-30 11:34 dpdklab
2024-05-30 11:34 dpdklab
2024-05-30 11:34 dpdklab
2024-05-30 11:34 dpdklab
2024-05-30 11:34 dpdklab
2024-05-30 11:33 dpdklab
2024-05-30 11:33 dpdklab
2024-05-30 11:33 dpdklab
2024-05-30 11:33 dpdklab
2024-05-30 11:33 dpdklab
2024-05-30 11:33 dpdklab
2024-05-30 11:33 dpdklab
2024-05-30 11:33 dpdklab
2024-05-30 11:32 dpdklab
2024-05-30 11:32 dpdklab
2024-05-30 11:32 dpdklab
2024-05-30 11:32 dpdklab
2024-05-30 11:32 dpdklab
2024-05-30 11:32 dpdklab
2024-05-30 11:31 dpdklab
2024-05-30 11:31 dpdklab
2024-05-30 11:31 dpdklab
2024-05-30 11:31 dpdklab
2024-05-30 11:31 dpdklab
2024-05-30 11:30 dpdklab
2024-05-30 11:30 dpdklab
2024-05-30 11:30 dpdklab
2024-05-30 11:29 dpdklab
2024-05-30 11:29 dpdklab
2024-05-30 11:29 dpdklab
2024-05-30 11:28 dpdklab
2024-05-30 11:28 dpdklab
2024-05-30 11:28 dpdklab
2024-05-30 11:28 dpdklab
2024-05-30 11:28 dpdklab
2024-05-30 11:27 dpdklab
2024-05-30 11:27 dpdklab
2024-05-30 11:26 dpdklab
2024-05-30 11:26 dpdklab
2024-05-30 11:26 dpdklab
2024-05-30 11:26 dpdklab
2024-05-30 11:25 dpdklab
2024-05-30 11:25 dpdklab
2024-05-30 11:24 dpdklab
2024-05-30 11:24 dpdklab
2024-05-30 11:24 dpdklab
2024-05-30 11:24 dpdklab
2024-05-30 11:23 dpdklab
2024-05-30 11:23 dpdklab
2024-05-30 11:23 dpdklab
2024-05-30 11:23 dpdklab
2024-05-30 11:21 dpdklab
2024-05-30 11:21 dpdklab
2024-05-30 11:21 dpdklab
2024-05-30 11:21 dpdklab
2024-05-30 11:20 dpdklab
2024-05-30 11:20 dpdklab
2024-05-30 11:20 dpdklab
2024-05-30 11:19 dpdklab
2024-05-30 11:19 dpdklab
2024-05-30 11:18 dpdklab
2024-05-30 11:17 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=6658d000.170a0220.f4fc2.0cafSMTPIN_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).