From: dpdklab@iol.unh.edu
To: Ali Alnubani <alialnu@nvidia.com>, Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@dpdk.org, 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] 9518bcf7000a62c06235634a07a563aa7f099fa4
Date: Mon, 18 Apr 2022 05:08:59 +0000 (UTC) [thread overview]
Message-ID: <20220418050859.45F2260217@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 1855 bytes --]
_Performance Testing PASS_
Branch: tags/v21.11
9518bcf7000a62c06235634a07a563aa7f099fa4 --> performance testing pass
Test environment and result as below:
Ubuntu 20.04
Kernel: 4.15.0-generic
Compiler: gcc 7.4
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.1% |
+------------+---------+----------+-------------+------------------------------+
| 128 | 256 | 1 | 1 | -0.2% |
+------------+---------+----------+-------------+------------------------------+
| 1024 | 256 | 1 | 1 | 0.2% |
+------------+---------+----------+-------------+------------------------------+
| 256 | 256 | 1 | 1 | -0.0% |
+------------+---------+----------+-------------+------------------------------+
| 1518 | 256 | 1 | 1 | -0.2% |
+------------+---------+----------+-------------+------------------------------+
| 512 | 256 | 1 | 1 | 0.5% |
+------------+---------+----------+-------------+------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/19492/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2022-04-18 5:09 UTC|newest]
Thread overview: 241+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-18 5:08 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-04-27 23:23 dpdklab
2022-04-26 17:36 dpdklab
2022-04-26 2:22 dpdklab
2022-04-26 1:31 dpdklab
2022-04-25 17:54 dpdklab
2022-04-25 6:00 dpdklab
2022-04-25 5:49 dpdklab
2022-04-25 5:42 dpdklab
2022-04-25 5:40 dpdklab
2022-04-25 5:38 dpdklab
2022-04-25 5:38 dpdklab
2022-04-25 5:37 dpdklab
2022-04-25 5:33 dpdklab
2022-04-25 5:20 dpdklab
2022-04-25 5:15 dpdklab
2022-04-24 6:09 dpdklab
2022-04-24 6:09 dpdklab
2022-04-24 6:02 dpdklab
2022-04-24 5:49 dpdklab
2022-04-24 5:41 dpdklab
2022-04-24 5:33 dpdklab
2022-04-24 5:21 dpdklab
2022-04-24 5:17 dpdklab
2022-04-24 5:11 dpdklab
2022-04-24 5:08 dpdklab
2022-04-23 7:10 dpdklab
2022-04-23 6:24 dpdklab
2022-04-23 6:14 dpdklab
2022-04-23 6:06 dpdklab
2022-04-23 5:40 dpdklab
2022-04-23 5:32 dpdklab
2022-04-23 5:20 dpdklab
2022-04-23 5:16 dpdklab
2022-04-23 5:09 dpdklab
2022-04-23 5:07 dpdklab
2022-04-22 9:27 dpdklab
2022-04-22 7:06 dpdklab
2022-04-22 6:45 dpdklab
2022-04-22 5:47 dpdklab
2022-04-22 5:39 dpdklab
2022-04-22 5:27 dpdklab
2022-04-22 5:21 dpdklab
2022-04-22 5:17 dpdklab
2022-04-22 5:17 dpdklab
2022-04-21 8:15 dpdklab
2022-04-21 7:50 dpdklab
2022-04-21 7:49 dpdklab
2022-04-21 7:49 dpdklab
2022-04-21 7:42 dpdklab
2022-04-21 5:42 dpdklab
2022-04-21 5:33 dpdklab
2022-04-21 5:22 dpdklab
2022-04-21 5:21 dpdklab
2022-04-21 5:10 dpdklab
2022-04-21 5:09 dpdklab
2022-04-20 7:23 dpdklab
2022-04-20 7:20 dpdklab
2022-04-20 7:12 dpdklab
2022-04-20 7:10 dpdklab
2022-04-20 6:59 dpdklab
2022-04-20 5:42 dpdklab
2022-04-20 5:34 dpdklab
2022-04-20 5:22 dpdklab
2022-04-20 5:22 dpdklab
2022-04-20 5:10 dpdklab
2022-04-20 5:08 dpdklab
2022-04-19 8:09 dpdklab
2022-04-19 7:23 dpdklab
2022-04-19 7:08 dpdklab
2022-04-19 6:40 dpdklab
2022-04-19 6:31 dpdklab
2022-04-19 5:41 dpdklab
2022-04-19 5:33 dpdklab
2022-04-19 5:21 dpdklab
2022-04-19 5:20 dpdklab
2022-04-19 5:10 dpdklab
2022-04-19 5:08 dpdklab
2022-04-19 0:06 dpdklab
2022-04-18 23:53 dpdklab
2022-04-18 22:47 dpdklab
2022-04-18 22:29 dpdklab
2022-04-18 21:54 dpdklab
2022-04-18 21:38 dpdklab
2022-04-18 19:05 dpdklab
2022-04-18 18:52 dpdklab
2022-04-18 7:18 dpdklab
2022-04-18 6:58 dpdklab
2022-04-18 6:35 dpdklab
2022-04-18 6:35 dpdklab
2022-04-18 6:31 dpdklab
2022-04-18 5:33 dpdklab
2022-04-18 5:13 dpdklab
2022-04-18 5:09 dpdklab
2022-04-17 6:30 dpdklab
2022-04-17 6:29 dpdklab
2022-04-17 6:18 dpdklab
2022-04-17 6:00 dpdklab
2022-04-17 5:34 dpdklab
2022-04-17 5:32 dpdklab
2022-04-17 5:25 dpdklab
2022-04-17 5:12 dpdklab
2022-04-17 5:08 dpdklab
2022-04-16 7:12 dpdklab
2022-04-16 7:00 dpdklab
2022-04-16 7:00 dpdklab
2022-04-16 6:52 dpdklab
2022-04-16 6:46 dpdklab
2022-04-16 5:32 dpdklab
2022-04-16 5:25 dpdklab
2022-04-16 5:10 dpdklab
2022-04-16 5:07 dpdklab
2022-04-15 10:30 dpdklab
2022-04-15 10:29 dpdklab
2022-04-15 10:20 dpdklab
2022-04-15 8:38 dpdklab
2022-04-15 7:40 dpdklab
2022-04-15 5:40 dpdklab
2022-04-15 5:32 dpdklab
2022-04-15 5:11 dpdklab
2022-04-15 5:07 dpdklab
2022-04-14 7:47 dpdklab
2022-04-14 7:04 dpdklab
2022-04-14 6:58 dpdklab
2022-04-14 6:45 dpdklab
2022-04-14 6:44 dpdklab
2022-04-14 5:33 dpdklab
2022-04-14 5:25 dpdklab
2022-04-14 5:12 dpdklab
2022-04-14 5:09 dpdklab
2022-04-14 5:08 dpdklab
2022-04-14 5:08 dpdklab
2022-04-13 7:02 dpdklab
2022-04-13 7:01 dpdklab
2022-04-13 6:56 dpdklab
2022-04-13 6:47 dpdklab
2022-04-13 6:41 dpdklab
2022-04-13 5:32 dpdklab
2022-04-13 5:25 dpdklab
2022-04-13 5:24 dpdklab
2022-04-13 5:10 dpdklab
2022-04-13 5:08 dpdklab
2022-04-13 5:08 dpdklab
2022-04-13 1:27 dpdklab
2022-04-13 1:07 dpdklab
2022-04-12 19:43 dpdklab
2022-04-12 19:36 dpdklab
2022-04-12 19:32 dpdklab
2022-04-12 19:16 dpdklab
2022-04-12 16:11 dpdklab
2022-04-12 16:04 dpdklab
2022-04-12 14:39 dpdklab
2022-04-12 14:23 dpdklab
2022-04-12 13:07 dpdklab
2022-04-12 12:47 dpdklab
2022-04-12 11:43 dpdklab
2022-04-12 11:27 dpdklab
2022-04-12 10:42 dpdklab
2022-04-12 9:07 dpdklab
2022-04-12 8:51 dpdklab
2022-04-12 7:45 dpdklab
2022-04-12 7:41 dpdklab
2022-04-12 7:21 dpdklab
2022-04-12 7:06 dpdklab
2022-04-12 7:00 dpdklab
2022-04-12 6:52 dpdklab
2022-04-12 5:55 dpdklab
2022-04-12 5:11 dpdklab
2022-04-12 4:20 dpdklab
2022-04-12 2:54 dpdklab
2022-04-12 2:34 dpdklab
2022-04-12 1:17 dpdklab
2022-04-12 1:02 dpdklab
2022-04-11 23:07 dpdklab
2022-04-11 9:55 dpdklab
2022-04-11 9:06 dpdklab
2022-04-11 8:20 dpdklab
2022-04-11 7:58 dpdklab
2022-04-11 6:05 dpdklab
2022-04-11 5:10 dpdklab
2022-04-10 7:04 dpdklab
2022-04-10 7:00 dpdklab
2022-04-10 6:53 dpdklab
2022-04-10 6:50 dpdklab
2022-04-10 5:08 dpdklab
2022-04-09 10:58 dpdklab
2022-04-09 8:00 dpdklab
2022-04-09 7:44 dpdklab
2022-04-09 7:31 dpdklab
2022-04-09 7:20 dpdklab
2022-04-09 5:10 dpdklab
2022-04-08 9:08 dpdklab
2022-04-08 7:08 dpdklab
2022-04-08 7:08 dpdklab
2022-04-08 6:48 dpdklab
2022-04-08 6:48 dpdklab
2022-04-08 5:09 dpdklab
2022-04-07 14:16 dpdklab
2022-04-07 14:15 dpdklab
2022-04-07 7:12 dpdklab
2022-04-07 7:08 dpdklab
2022-04-07 6:59 dpdklab
2022-04-07 5:33 dpdklab
2022-04-07 5:26 dpdklab
2022-04-07 5:25 dpdklab
2022-04-07 5:18 dpdklab
2022-04-07 5:12 dpdklab
2022-04-07 5:08 dpdklab
2022-04-06 7:50 dpdklab
2022-04-06 7:09 dpdklab
2022-04-06 6:55 dpdklab
2022-04-06 6:51 dpdklab
2022-04-06 6:49 dpdklab
2022-04-06 5:33 dpdklab
2022-04-06 5:27 dpdklab
2022-04-06 5:26 dpdklab
2022-04-06 5:10 dpdklab
2022-04-06 5:09 dpdklab
2022-04-06 5:09 dpdklab
2022-04-05 7:52 dpdklab
2022-04-05 7:12 dpdklab
2022-04-05 6:56 dpdklab
2022-04-05 6:49 dpdklab
2022-04-05 6:47 dpdklab
2022-04-05 5:32 dpdklab
2022-04-05 5:24 dpdklab
2022-04-05 5:17 dpdklab
2022-04-05 5:13 dpdklab
2022-04-05 5:08 dpdklab
2022-04-05 5:07 dpdklab
2022-04-05 4:30 dpdklab
2022-04-05 4:08 dpdklab
2022-04-05 3:51 dpdklab
2022-04-05 3:49 dpdklab
2022-04-05 3:17 dpdklab
2022-04-05 3:15 dpdklab
2022-04-05 3:11 dpdklab
2022-04-05 3:08 dpdklab
2022-04-05 3:01 dpdklab
2022-04-05 2:56 dpdklab
2022-04-05 2:55 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=20220418050859.45F2260217@dpdk-ubuntu.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=alialnu@nvidia.com \
--cc=bluca@debian.org \
--cc=christian.ehrhardt@canonical.com \
--cc=dpdk-test-reports@dpdk.org \
--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).