From: dpdklab@iol.unh.edu
To: Ali Alnubani <alialnu@nvidia.com>, Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu, Chenbo Xia <chenbox@nvidia.com>,
Maxime Coquelin <maxime.coquelin@redhat.com>
Subject: |SUCCESS| [GIT MASTER] 07e3bebf3c93750c52ed9be87edd212fbc22da0a
Date: Thu, 21 Nov 2024 12:06:40 -0800 (PST) [thread overview]
Message-ID: <673f92d0.050a0220.27458a.0cb5SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Performance Testing PASS_
Branch: dpdk-next-virtio
07e3bebf3c93750c52ed9be87edd212fbc22da0a --> performance testing pass
Upstream job id: Template-DTS-Pipeline#198130
Test environment and result as below:
Ubuntu 24.04
Kernel: 6.8.0-45-generic
Compiler: gcc 13.2.0
NIC: NVIDIA Mellanox ConnectX-7 100000 Mbps
Fail/Total: 0/6
Detail performance results:
+------------+---------+----------+-------------+------------------------------+
| frame_size | txd/rxd | num_cpus | num_threads | throughput difference from |
| | | | | expected |
+============+=========+==========+=============+==============================+
| 64 | 1024 | 1 | 1 | -0.5% |
+------------+---------+----------+-------------+------------------------------+
| 128 | 1024 | 1 | 1 | -0.6% |
+------------+---------+----------+-------------+------------------------------+
| 256 | 1024 | 1 | 1 | -1.5% |
+------------+---------+----------+-------------+------------------------------+
| 512 | 1024 | 1 | 1 | 0.2% |
+------------+---------+----------+-------------+------------------------------+
| 1024 | 1024 | 1 | 1 | -0.1% |
+------------+---------+----------+-------------+------------------------------+
| 1518 | 1024 | 1 | 1 | 0.2% |
+------------+---------+----------+-------------+------------------------------+
Ubuntu 24.04
Kernel: 6.8.0-45-generic
Compiler: gcc 13.2.0
NIC: Mellanox ConnectX-6 Lx 25000 Mbps
Fail/Total: 0/6
Detail performance results:
+------------+---------+----------+-------------+------------------------------+
| frame_size | txd/rxd | num_cpus | num_threads | throughput difference from |
| | | | | expected |
+============+=========+==========+=============+==============================+
| 64 | 1024 | 1 | 1 | -0.3% |
+------------+---------+----------+-------------+------------------------------+
| 128 | 1024 | 1 | 1 | -0.2% |
+------------+---------+----------+-------------+------------------------------+
| 256 | 1024 | 1 | 1 | -0.1% |
+------------+---------+----------+-------------+------------------------------+
| 512 | 1024 | 1 | 1 | 0.3% |
+------------+---------+----------+-------------+------------------------------+
| 1024 | 1024 | 1 | 1 | 0.2% |
+------------+---------+----------+-------------+------------------------------+
| 1518 | 1024 | 1 | 1 | 0.1% |
+------------+---------+----------+-------------+------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/31675/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-11-21 20:06 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-21 20:06 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-11-22 0:31 dpdklab
2024-11-22 0:17 dpdklab
2024-11-22 0:14 dpdklab
2024-11-22 0:07 dpdklab
2024-11-22 0:05 dpdklab
2024-11-21 23:58 dpdklab
2024-11-21 23:51 dpdklab
2024-11-21 22:47 dpdklab
2024-11-21 22:24 dpdklab
2024-11-21 22:13 dpdklab
2024-11-21 21:46 dpdklab
2024-11-21 21:19 dpdklab
2024-11-21 21:16 dpdklab
2024-11-21 20:37 dpdklab
2024-11-21 20:18 dpdklab
2024-11-21 18:52 dpdklab
2024-11-19 18:26 dpdklab
2024-11-19 12:03 dpdklab
2024-11-19 11:38 dpdklab
2024-11-19 11:04 dpdklab
2024-11-19 10:47 dpdklab
2024-11-19 10:15 dpdklab
2024-11-19 10:11 dpdklab
2024-11-19 9:58 dpdklab
2024-11-19 9:43 dpdklab
2024-11-19 8:56 dpdklab
2024-11-19 7:58 dpdklab
2024-11-19 7:48 dpdklab
2024-11-19 7:34 dpdklab
2024-11-19 7:11 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=673f92d0.050a0220.27458a.0cb5SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=alialnu@nvidia.com \
--cc=chenbox@nvidia.com \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=maxime.coquelin@redhat.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).