From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| [GIT MASTER] 0d761dfc89b71fa46193a545cce3fbe2613856a6
Date: Fri, 31 May 2024 04:06:58 -0700 (PDT) [thread overview]
Message-ID: <6659af52.050a0220.ae385.5ad5SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Performance Testing PASS_
Branch: dpdk-next-net-intel
0d761dfc89b71fa46193a545cce3fbe2613856a6 --> 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.6% |
+------------+---------+----------+-------------+------------------------------+
| 128 | 256 | 1 | 1 | -0.1% |
+------------+---------+----------+-------------+------------------------------+
| 1024 | 256 | 1 | 1 | -0.0% |
+------------+---------+----------+-------------+------------------------------+
| 256 | 256 | 1 | 1 | -0.2% |
+------------+---------+----------+-------------+------------------------------+
| 1518 | 256 | 1 | 1 | 0.1% |
+------------+---------+----------+-------------+------------------------------+
| 512 | 256 | 1 | 1 | 0.6% |
+------------+---------+----------+-------------+------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/29271/
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-31 11:07 UTC|newest]
Thread overview: 83+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-31 11:06 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-05-31 13:55 dpdklab
2024-05-31 12:26 dpdklab
2024-05-31 12:15 dpdklab
2024-05-31 11:51 dpdklab
2024-05-31 11:45 dpdklab
2024-05-31 11:42 dpdklab
2024-05-31 11:39 dpdklab
2024-05-31 11:37 dpdklab
2024-05-31 11:34 dpdklab
2024-05-31 11:31 dpdklab
2024-05-31 11:31 dpdklab
2024-05-31 11:29 dpdklab
2024-05-31 11:28 dpdklab
2024-05-31 11:27 dpdklab
2024-05-31 11:25 dpdklab
2024-05-31 11:23 dpdklab
2024-05-31 11:23 dpdklab
2024-05-31 11:23 dpdklab
2024-05-31 11:23 dpdklab
2024-05-31 11:22 dpdklab
2024-05-31 11:21 dpdklab
2024-05-31 11:20 dpdklab
2024-05-31 11:19 dpdklab
2024-05-31 11:17 dpdklab
2024-05-31 11:17 dpdklab
2024-05-31 11:16 dpdklab
2024-05-31 11:16 dpdklab
2024-05-31 11:16 dpdklab
2024-05-31 11:16 dpdklab
2024-05-31 11:15 dpdklab
2024-05-31 11:14 dpdklab
2024-05-31 11:14 dpdklab
2024-05-31 11:14 dpdklab
2024-05-31 11:13 dpdklab
2024-05-31 11:13 dpdklab
2024-05-31 11:13 dpdklab
2024-05-31 11:13 dpdklab
2024-05-31 11:13 dpdklab
2024-05-31 11:13 dpdklab
2024-05-31 11:13 dpdklab
2024-05-31 11:12 dpdklab
2024-05-31 11:12 dpdklab
2024-05-31 11:12 dpdklab
2024-05-31 11:12 dpdklab
2024-05-31 11:12 dpdklab
2024-05-31 11:12 dpdklab
2024-05-31 11:12 dpdklab
2024-05-31 11:11 dpdklab
2024-05-31 11:11 dpdklab
2024-05-31 11:11 dpdklab
2024-05-31 11:11 dpdklab
2024-05-31 11:11 dpdklab
2024-05-31 11:11 dpdklab
2024-05-31 11:11 dpdklab
2024-05-31 11:10 dpdklab
2024-05-31 11:10 dpdklab
2024-05-31 11:10 dpdklab
2024-05-31 11:10 dpdklab
2024-05-31 11:10 dpdklab
2024-05-31 11:10 dpdklab
2024-05-31 11:10 dpdklab
2024-05-31 11:10 dpdklab
2024-05-31 11:10 dpdklab
2024-05-31 11:09 dpdklab
2024-05-31 11:09 dpdklab
2024-05-31 11:08 dpdklab
2024-05-31 11:08 dpdklab
2024-05-31 11:08 dpdklab
2024-05-31 11:08 dpdklab
2024-05-31 11:08 dpdklab
2024-05-31 11:07 dpdklab
2024-05-31 11:07 dpdklab
2024-05-31 11:07 dpdklab
2024-05-31 11:07 dpdklab
2024-05-31 11:06 dpdklab
2024-05-31 11:06 dpdklab
2024-05-31 11:06 dpdklab
2024-05-31 11:06 dpdklab
2024-05-31 11:06 dpdklab
2024-05-31 11:06 dpdklab
2024-05-31 11:05 dpdklab
2024-05-31 11: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=6659af52.050a0220.ae385.5ad5SMTPIN_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).