From: dpdklab@iol.unh.edu
To: Ali Alnubani <alialnu@nvidia.com>, Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu, Xueming Li <xuemingl@nvidia.com>,
Christian Ehrhardt <christian.ehrhardt@canonical.com>,
Kevin Traynor <ktraynor@redhat.com>,
Luca Boccassi <bluca@debian.org>
Subject: |SUCCESS| [GIT MASTER] 782b5a22bc45e37565b4731659a2f406cbe442de
Date: Wed, 13 Mar 2024 22:32:13 -0700 (PDT) [thread overview]
Message-ID: <65f28bdd.a70a0220.5995e.2c27SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Performance Testing PASS_
Branch: tags/v22.11
782b5a22bc45e37565b4731659a2f406cbe442de --> performance testing pass
Test environment and result as below:
Ubuntu 22.04
Kernel: 5.15.0-78-generic
Compiler: gcc 11.4.0
NIC: Mellanox ConnectX-5 100000 Mbps
Target: x86_64-native-linuxapp-gcc
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.2% |
+------------+---------+----------+-------------+------------------------------+
| 1024 | 256 | 1 | 1 | -0.1% |
+------------+---------+----------+-------------+------------------------------+
| 256 | 256 | 1 | 1 | -0.0% |
+------------+---------+----------+-------------+------------------------------+
| 1518 | 256 | 1 | 1 | -0.1% |
+------------+---------+----------+-------------+------------------------------+
| 512 | 256 | 1 | 1 | 0.4% |
+------------+---------+----------+-------------+------------------------------+
Ubuntu 22.04
Kernel: 5.15.0-78-generic
Compiler: gcc 11.4.0
NIC: Mellanox ConnectX-6 Lx 25000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/6
Detail performance results:
+------------+---------+----------+-------------+------------------------------+
| frame_size | txd/rxd | num_cpus | num_threads | throughput difference from |
| | | | | expected |
+============+=========+==========+=============+==============================+
| 64 | 256 | 1 | 1 | 0.1% |
+------------+---------+----------+-------------+------------------------------+
| 128 | 256 | 1 | 1 | 0.1% |
+------------+---------+----------+-------------+------------------------------+
| 1024 | 256 | 1 | 1 | -0.2% |
+------------+---------+----------+-------------+------------------------------+
| 256 | 256 | 1 | 1 | 0.0% |
+------------+---------+----------+-------------+------------------------------+
| 1518 | 256 | 1 | 1 | 0.1% |
+------------+---------+----------+-------------+------------------------------+
| 512 | 256 | 1 | 1 | 0.3% |
+------------+---------+----------+-------------+------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/28478/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-03-14 5:37 UTC|newest]
Thread overview: 361+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-14 5:32 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-03-20 8:10 dpdklab
2024-03-20 6:43 dpdklab
2024-03-20 0:43 dpdklab
2024-03-19 23:56 dpdklab
2024-03-19 12:51 dpdklab
2024-03-19 12:03 dpdklab
2024-03-18 23:52 dpdklab
2024-03-18 23:08 dpdklab
2024-03-18 6:27 dpdklab
2024-03-18 5:45 dpdklab
2024-03-18 5:43 dpdklab
2024-03-18 5:41 dpdklab
2024-03-18 5:37 dpdklab
2024-03-18 5:35 dpdklab
2024-03-18 5:35 dpdklab
2024-03-18 5:35 dpdklab
2024-03-18 5:34 dpdklab
2024-03-18 5:33 dpdklab
2024-03-18 5:30 dpdklab
2024-03-18 5:30 dpdklab
2024-03-18 5:30 dpdklab
2024-03-18 5:29 dpdklab
2024-03-18 5:26 dpdklab
2024-03-18 5:22 dpdklab
2024-03-18 5:22 dpdklab
2024-03-18 5:20 dpdklab
2024-03-18 5:20 dpdklab
2024-03-18 5:20 dpdklab
2024-03-18 5:19 dpdklab
2024-03-18 5:18 dpdklab
2024-03-18 5:16 dpdklab
2024-03-18 5:16 dpdklab
2024-03-18 5:15 dpdklab
2024-03-18 5:15 dpdklab
2024-03-18 5:14 dpdklab
2024-03-18 5:13 dpdklab
2024-03-18 5:13 dpdklab
2024-03-18 5:12 dpdklab
2024-03-18 5:12 dpdklab
2024-03-18 5:12 dpdklab
2024-03-18 5:12 dpdklab
2024-03-18 5:11 dpdklab
2024-03-18 5:11 dpdklab
2024-03-18 5:10 dpdklab
2024-03-18 5:10 dpdklab
2024-03-18 5:10 dpdklab
2024-03-18 5:09 dpdklab
2024-03-18 5:09 dpdklab
2024-03-18 5:08 dpdklab
2024-03-18 5:08 dpdklab
2024-03-18 5:08 dpdklab
2024-03-18 5:08 dpdklab
2024-03-18 5:07 dpdklab
2024-03-18 5:07 dpdklab
2024-03-18 5:07 dpdklab
2024-03-18 5:07 dpdklab
2024-03-18 5:04 dpdklab
2024-03-18 4:59 dpdklab
2024-03-18 4:56 dpdklab
2024-03-17 20:49 dpdklab
2024-03-17 20:06 dpdklab
2024-03-17 8:09 dpdklab
2024-03-17 6:41 dpdklab
2024-03-17 6:33 dpdklab
2024-03-17 6:31 dpdklab
2024-03-17 6:20 dpdklab
2024-03-17 6:14 dpdklab
2024-03-17 6:13 dpdklab
2024-03-17 6:06 dpdklab
2024-03-17 6:04 dpdklab
2024-03-17 6:00 dpdklab
2024-03-17 5:59 dpdklab
2024-03-17 5:55 dpdklab
2024-03-17 5:53 dpdklab
2024-03-17 5:51 dpdklab
2024-03-17 5:48 dpdklab
2024-03-17 5:45 dpdklab
2024-03-17 5:43 dpdklab
2024-03-17 5:42 dpdklab
2024-03-17 5:38 dpdklab
2024-03-17 5:38 dpdklab
2024-03-17 5:37 dpdklab
2024-03-17 5:36 dpdklab
2024-03-17 5:36 dpdklab
2024-03-17 5:34 dpdklab
2024-03-17 5:34 dpdklab
2024-03-17 5:32 dpdklab
2024-03-17 5:32 dpdklab
2024-03-17 5:31 dpdklab
2024-03-17 5:28 dpdklab
2024-03-17 5:27 dpdklab
2024-03-17 5:25 dpdklab
2024-03-17 5:24 dpdklab
2024-03-17 5:24 dpdklab
2024-03-17 5:24 dpdklab
2024-03-17 5:24 dpdklab
2024-03-17 5:22 dpdklab
2024-03-17 5:21 dpdklab
2024-03-17 5:20 dpdklab
2024-03-17 5:19 dpdklab
2024-03-17 5:18 dpdklab
2024-03-17 5:18 dpdklab
2024-03-17 5:18 dpdklab
2024-03-17 5:17 dpdklab
2024-03-17 5:17 dpdklab
2024-03-17 5:17 dpdklab
2024-03-17 5:17 dpdklab
2024-03-17 5:16 dpdklab
2024-03-17 5:16 dpdklab
2024-03-17 5:15 dpdklab
2024-03-17 5:14 dpdklab
2024-03-16 17:10 dpdklab
2024-03-16 16:23 dpdklab
2024-03-16 7:54 dpdklab
2024-03-16 6:28 dpdklab
2024-03-16 6:28 dpdklab
2024-03-16 6:25 dpdklab
2024-03-16 6:17 dpdklab
2024-03-16 6:11 dpdklab
2024-03-16 6:10 dpdklab
2024-03-16 6:10 dpdklab
2024-03-16 6:02 dpdklab
2024-03-16 6:00 dpdklab
2024-03-16 5:58 dpdklab
2024-03-16 5:57 dpdklab
2024-03-16 5:53 dpdklab
2024-03-16 5:51 dpdklab
2024-03-16 5:47 dpdklab
2024-03-16 5:44 dpdklab
2024-03-16 5:42 dpdklab
2024-03-16 5:39 dpdklab
2024-03-16 5:37 dpdklab
2024-03-16 5:32 dpdklab
2024-03-16 5:16 dpdklab
2024-03-16 5:12 dpdklab
2024-03-16 5:05 dpdklab
2024-03-16 4:56 dpdklab
2024-03-16 4:54 dpdklab
2024-03-16 4:48 dpdklab
2024-03-16 4:46 dpdklab
2024-03-16 4:46 dpdklab
2024-03-16 4:43 dpdklab
2024-03-16 4:42 dpdklab
2024-03-16 4:40 dpdklab
2024-03-16 4:39 dpdklab
2024-03-16 4:39 dpdklab
2024-03-16 4:38 dpdklab
2024-03-16 4:38 dpdklab
2024-03-16 4:37 dpdklab
2024-03-16 4:37 dpdklab
2024-03-16 4:33 dpdklab
2024-03-16 4:32 dpdklab
2024-03-16 4:31 dpdklab
2024-03-16 4:27 dpdklab
2024-03-16 4:27 dpdklab
2024-03-16 4:27 dpdklab
2024-03-16 4:26 dpdklab
2024-03-16 4:26 dpdklab
2024-03-16 4:26 dpdklab
2024-03-16 4:26 dpdklab
2024-03-16 4:25 dpdklab
2024-03-16 4:24 dpdklab
2024-03-16 4:24 dpdklab
2024-03-15 8:52 dpdklab
2024-03-15 8:38 dpdklab
2024-03-15 7:54 dpdklab
2024-03-15 7:45 dpdklab
2024-03-15 7:23 dpdklab
2024-03-15 7:21 dpdklab
2024-03-15 7:18 dpdklab
2024-03-15 7:18 dpdklab
2024-03-15 7:17 dpdklab
2024-03-15 7:15 dpdklab
2024-03-15 7:14 dpdklab
2024-03-15 7:14 dpdklab
2024-03-15 7:05 dpdklab
2024-03-15 7:02 dpdklab
2024-03-15 7:02 dpdklab
2024-03-15 7:01 dpdklab
2024-03-15 7:00 dpdklab
2024-03-15 6:59 dpdklab
2024-03-15 6:43 dpdklab
2024-03-15 6:42 dpdklab
2024-03-15 6:25 dpdklab
2024-03-15 6:25 dpdklab
2024-03-15 6:24 dpdklab
2024-03-15 6:24 dpdklab
2024-03-15 6:13 dpdklab
2024-03-15 6:11 dpdklab
2024-03-15 6:10 dpdklab
2024-03-15 6:09 dpdklab
2024-03-15 6:08 dpdklab
2024-03-15 6:06 dpdklab
2024-03-15 6:04 dpdklab
2024-03-15 6:03 dpdklab
2024-03-15 6:01 dpdklab
2024-03-15 5:59 dpdklab
2024-03-15 5:49 dpdklab
2024-03-15 5:48 dpdklab
2024-03-15 5:48 dpdklab
2024-03-15 5:46 dpdklab
2024-03-15 5:44 dpdklab
2024-03-15 5:43 dpdklab
2024-03-15 5:43 dpdklab
2024-03-15 5:42 dpdklab
2024-03-15 5:41 dpdklab
2024-03-15 5:41 dpdklab
2024-03-15 5:37 dpdklab
2024-03-15 5:36 dpdklab
2024-03-15 5:33 dpdklab
2024-03-15 5:32 dpdklab
2024-03-15 5:31 dpdklab
2024-03-15 5:31 dpdklab
2024-03-15 5:28 dpdklab
2024-03-14 8:21 dpdklab
2024-03-14 6:50 dpdklab
2024-03-14 6:49 dpdklab
2024-03-14 6:49 dpdklab
2024-03-14 6:42 dpdklab
2024-03-14 6:26 dpdklab
2024-03-14 6:22 dpdklab
2024-03-14 6:17 dpdklab
2024-03-14 6:17 dpdklab
2024-03-14 6:15 dpdklab
2024-03-14 6:11 dpdklab
2024-03-14 6:10 dpdklab
2024-03-14 6:09 dpdklab
2024-03-14 6:01 dpdklab
2024-03-14 6:01 dpdklab
2024-03-14 6:00 dpdklab
2024-03-14 5:57 dpdklab
2024-03-14 5:53 dpdklab
2024-03-14 5:52 dpdklab
2024-03-14 5:50 dpdklab
2024-03-14 5:50 dpdklab
2024-03-14 5:50 dpdklab
2024-03-14 5:50 dpdklab
2024-03-14 5:47 dpdklab
2024-03-14 5:47 dpdklab
2024-03-14 5:47 dpdklab
2024-03-14 5:46 dpdklab
2024-03-14 5:46 dpdklab
2024-03-14 5:46 dpdklab
2024-03-14 5:45 dpdklab
2024-03-14 5:39 dpdklab
2024-03-14 5:38 dpdklab
2024-03-14 5:37 dpdklab
2024-03-14 5:35 dpdklab
2024-03-14 5:31 dpdklab
2024-03-14 5:31 dpdklab
2024-03-14 5:21 dpdklab
2024-03-14 5:19 dpdklab
2024-03-14 5:18 dpdklab
2024-03-14 5:18 dpdklab
2024-03-14 5:17 dpdklab
2024-03-14 5:15 dpdklab
2024-03-14 5:15 dpdklab
2024-03-14 5:13 dpdklab
2024-03-14 5:13 dpdklab
2024-03-14 5:12 dpdklab
2024-03-14 5:10 dpdklab
2024-03-14 5:10 dpdklab
2024-03-14 5:07 dpdklab
2024-03-14 5:03 dpdklab
2024-03-14 5:00 dpdklab
2024-03-13 8:46 dpdklab
2024-03-13 8:30 dpdklab
2024-03-13 6:59 dpdklab
2024-03-13 6:59 dpdklab
2024-03-13 6:57 dpdklab
2024-03-13 6:56 dpdklab
2024-03-13 6:55 dpdklab
2024-03-13 6:53 dpdklab
2024-03-13 6:53 dpdklab
2024-03-13 6:49 dpdklab
2024-03-13 6:49 dpdklab
2024-03-13 6:19 dpdklab
2024-03-13 6:15 dpdklab
2024-03-13 6:12 dpdklab
2024-03-13 6:12 dpdklab
2024-03-13 6:09 dpdklab
2024-03-13 6:09 dpdklab
2024-03-13 6:08 dpdklab
2024-03-13 6:05 dpdklab
2024-03-13 6:05 dpdklab
2024-03-13 6:01 dpdklab
2024-03-13 5:59 dpdklab
2024-03-13 5:58 dpdklab
2024-03-13 5:50 dpdklab
2024-03-13 5:50 dpdklab
2024-03-13 5:46 dpdklab
2024-03-13 5:45 dpdklab
2024-03-13 5:44 dpdklab
2024-03-13 5:41 dpdklab
2024-03-13 5:40 dpdklab
2024-03-13 5:39 dpdklab
2024-03-13 5:39 dpdklab
2024-03-13 5:38 dpdklab
2024-03-13 5:31 dpdklab
2024-03-13 5:30 dpdklab
2024-03-13 5:27 dpdklab
2024-03-13 5:27 dpdklab
2024-03-13 5:25 dpdklab
2024-03-13 5:24 dpdklab
2024-03-13 4:57 dpdklab
2024-03-13 4:49 dpdklab
2024-03-13 4:45 dpdklab
2024-03-13 4:34 dpdklab
2024-03-13 4:33 dpdklab
2024-03-13 4:32 dpdklab
2024-03-13 4:31 dpdklab
2024-03-13 4:30 dpdklab
2024-03-13 4:29 dpdklab
2024-03-13 4:27 dpdklab
2024-03-13 4:26 dpdklab
2024-03-13 4:24 dpdklab
2024-03-12 9:03 dpdklab
2024-03-12 8:35 dpdklab
2024-03-12 8:32 dpdklab
2024-03-12 8:31 dpdklab
2024-03-12 8:25 dpdklab
2024-03-12 6:56 dpdklab
2024-03-12 6:55 dpdklab
2024-03-12 6:50 dpdklab
2024-03-12 6:49 dpdklab
2024-03-12 6:47 dpdklab
2024-03-12 6:33 dpdklab
2024-03-12 6:26 dpdklab
2024-03-12 6:23 dpdklab
2024-03-12 6:23 dpdklab
2024-03-12 6:21 dpdklab
2024-03-12 6:18 dpdklab
2024-03-12 6:16 dpdklab
2024-03-12 6:15 dpdklab
2024-03-12 6:05 dpdklab
2024-03-12 6:05 dpdklab
2024-03-12 6:04 dpdklab
2024-03-12 6:03 dpdklab
2024-03-12 6:01 dpdklab
2024-03-12 6:01 dpdklab
2024-03-12 6:00 dpdklab
2024-03-12 5:58 dpdklab
2024-03-12 5:57 dpdklab
2024-03-12 5:56 dpdklab
2024-03-12 5:54 dpdklab
2024-03-12 5:52 dpdklab
2024-03-12 5:51 dpdklab
2024-03-12 5:35 dpdklab
2024-03-12 5:32 dpdklab
2024-03-12 5:29 dpdklab
2024-03-12 5:27 dpdklab
2024-03-12 5:27 dpdklab
2024-03-12 5:26 dpdklab
2024-03-12 5:25 dpdklab
2024-03-12 5:25 dpdklab
2024-03-12 5:25 dpdklab
2024-03-12 5:25 dpdklab
2024-03-12 5:23 dpdklab
2024-03-12 5:20 dpdklab
2024-03-12 5:20 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=65f28bdd.a70a0220.5995e.2c27SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=alialnu@nvidia.com \
--cc=bluca@debian.org \
--cc=christian.ehrhardt@canonical.com \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=ktraynor@redhat.com \
--cc=test-report@dpdk.org \
--cc=xuemingl@nvidia.com \
/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).