From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu, Akhil Goyal <gakhil@marvell.com>
Subject: |SUCCESS| [GIT MASTER] edd3f4b1265e6da707c46ca9b6c39d332647baea
Date: Tue, 01 Apr 2025 13:26:56 -0700 (PDT) [thread overview]
Message-ID: <67ec4c10.050a0220.3ccf7c.df8dSMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Performance Testing PASS_
Branch: dpdk-next-crypto
edd3f4b1265e6da707c46ca9b6c39d332647baea --> performance testing pass
Upstream job id: Template-DTS-Pipeline#219845
Test environment and result as below:
Ubuntu 22.04
Kernel: 5.15.0-131-generic
Compiler: gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
NIC: Intel Corporation Ethernet Converged Network Adapter 82599ES 10000 Mbps
Fail/Total: 0/6
Detail performance results:
+----------+-------------+---------+------------+------------------------------+
| num_cpus | num_threads | txd/rxd | frame_size | throughput difference from |
| | | | | expected |
+==========+=============+=========+============+==============================+
| 1 | 2 | 128 | 64 | -0.1% |
+----------+-------------+---------+------------+------------------------------+
| 1 | 2 | 512 | 64 | -0.1% |
+----------+-------------+---------+------------+------------------------------+
| 1 | 2 | 2048 | 64 | 0.2% |
+----------+-------------+---------+------------+------------------------------+
| 1 | 1 | 128 | 64 | -0.0% |
+----------+-------------+---------+------------+------------------------------+
| 1 | 1 | 512 | 64 | -0.2% |
+----------+-------------+---------+------------+------------------------------+
| 1 | 1 | 2048 | 64 | 0.5% |
+----------+-------------+---------+------------+------------------------------+
Ubuntu 20.04
Kernel: 5.4.0-122-generic
Compiler: gcc 9.4.0
NIC: Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Fail/Total: 0/4
Detail performance results:
+----------+-------------+---------+------------+------------------------------+
| num_cpus | num_threads | txd/rxd | frame_size | throughput difference from |
| | | | | expected |
+==========+=============+=========+============+==============================+
| 1 | 2 | 512 | 64 | 0.2% |
+----------+-------------+---------+------------+------------------------------+
| 1 | 2 | 2048 | 64 | 3.6% |
+----------+-------------+---------+------------+------------------------------+
| 1 | 1 | 512 | 64 | -3.5% |
+----------+-------------+---------+------------+------------------------------+
| 1 | 1 | 2048 | 64 | -0.6% |
+----------+-------------+---------+------------+------------------------------+
Ubuntu 24.04
Kernel: 6.8.0-52-generic
Compiler: gcc 13.3.0
NIC: Intel E810 (Arm Grace Server) 100000 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.1% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 2048 | 1 | 1 | -1.3% |
+------------+---------+----------+-------------+------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/33118/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2025-04-01 20:26 UTC|newest]
Thread overview: 72+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-01 20:26 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-04-02 2:58 dpdklab
2025-04-02 2:17 dpdklab
2025-04-02 2:12 dpdklab
2025-04-02 2:06 dpdklab
2025-04-02 2:02 dpdklab
2025-04-02 1:55 dpdklab
2025-04-02 1:37 dpdklab
2025-04-02 1:37 dpdklab
2025-04-02 1:30 dpdklab
2025-04-02 1:20 dpdklab
2025-04-02 1:20 dpdklab
2025-04-02 1:10 dpdklab
2025-04-02 1:07 dpdklab
2025-04-02 1:04 dpdklab
2025-04-02 0:42 dpdklab
2025-04-02 0:37 dpdklab
2025-04-01 23:24 dpdklab
2025-04-01 21:57 dpdklab
2025-04-01 20:50 dpdklab
2025-04-01 20:49 dpdklab
2025-04-01 20:44 dpdklab
2025-04-01 20:43 dpdklab
2025-04-01 20:42 dpdklab
2025-04-01 20:34 dpdklab
2025-04-01 20:25 dpdklab
2025-04-01 20:18 dpdklab
2025-04-01 20:14 dpdklab
2025-04-01 20:12 dpdklab
2025-04-01 20:11 dpdklab
2025-04-01 2:21 dpdklab
2025-04-01 1:39 dpdklab
2025-04-01 1:22 dpdklab
2025-04-01 1:07 dpdklab
2025-04-01 1:06 dpdklab
2025-04-01 1:04 dpdklab
2025-04-01 0:58 dpdklab
2025-04-01 0:54 dpdklab
2025-04-01 0:45 dpdklab
2025-04-01 0:42 dpdklab
2025-04-01 0:31 dpdklab
2025-04-01 0:31 dpdklab
2025-04-01 0:29 dpdklab
2025-03-30 2:05 dpdklab
2025-03-30 1:32 dpdklab
2025-03-30 1:28 dpdklab
2025-03-30 1:17 dpdklab
2025-03-30 1:12 dpdklab
2025-03-30 1:04 dpdklab
2025-03-30 1:04 dpdklab
2025-03-30 0:57 dpdklab
2025-03-30 0:44 dpdklab
2025-03-30 0:42 dpdklab
2025-03-30 0:29 dpdklab
2025-03-30 0:28 dpdklab
2025-03-30 0:28 dpdklab
2025-03-30 0:28 dpdklab
2025-03-29 6:14 dpdklab
2025-03-28 21:07 dpdklab
2025-03-28 3:02 dpdklab
2025-03-28 3:01 dpdklab
2025-03-28 1:45 dpdklab
2025-03-28 1:41 dpdklab
2025-03-28 1:41 dpdklab
2025-03-28 1:35 dpdklab
2025-03-28 1:27 dpdklab
2025-03-28 1:21 dpdklab
2025-03-28 1:14 dpdklab
2025-03-28 1:10 dpdklab
2025-03-28 1:05 dpdklab
2025-03-28 1:03 dpdklab
2025-03-28 0:52 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=67ec4c10.050a0220.3ccf7c.df8dSMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=gakhil@marvell.com \
--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).