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] e9b46ab763a148b85500d591122000e89fd3a002
Date: Thu, 26 May 2022 05:08:51 +0000 (UTC) [thread overview]
Message-ID: <20220526050851.5012D600A8@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 1855 bytes --]
_Performance Testing PASS_
Branch: tags/v21.11
e9b46ab763a148b85500d591122000e89fd3a002 --> 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.1% |
+------------+---------+----------+-------------+------------------------------+
| 1024 | 256 | 1 | 1 | -0.0% |
+------------+---------+----------+-------------+------------------------------+
| 256 | 256 | 1 | 1 | -0.3% |
+------------+---------+----------+-------------+------------------------------+
| 1518 | 256 | 1 | 1 | 0.0% |
+------------+---------+----------+-------------+------------------------------+
| 512 | 256 | 1 | 1 | 0.3% |
+------------+---------+----------+-------------+------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/19997/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2022-05-26 5:08 UTC|newest]
Thread overview: 140+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-26 5:08 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-06-05 13:51 dpdklab
2022-06-04 12:22 dpdklab
2022-06-04 5:12 dpdklab
2022-06-01 5:44 dpdklab
2022-06-01 5:28 dpdklab
2022-05-31 19:19 dpdklab
2022-05-31 19:02 dpdklab
2022-05-31 17:40 dpdklab
2022-05-31 17:28 dpdklab
2022-05-31 16:25 dpdklab
2022-05-31 16:10 dpdklab
2022-05-31 15:25 dpdklab
2022-05-31 9:01 dpdklab
2022-05-31 8:54 dpdklab
2022-05-31 8:13 dpdklab
2022-05-31 6:20 dpdklab
2022-05-31 5:41 dpdklab
2022-05-31 5:21 dpdklab
2022-05-31 5:09 dpdklab
2022-05-31 5:09 dpdklab
2022-05-30 7:37 dpdklab
2022-05-30 6:49 dpdklab
2022-05-30 6:47 dpdklab
2022-05-30 6:36 dpdklab
2022-05-30 6:35 dpdklab
2022-05-30 5:41 dpdklab
2022-05-30 5:29 dpdklab
2022-05-30 5:09 dpdklab
2022-05-30 5:08 dpdklab
2022-05-29 18:19 dpdklab
2022-05-29 15:16 dpdklab
2022-05-29 11:08 dpdklab
2022-05-29 8:00 dpdklab
2022-05-29 6:59 dpdklab
2022-05-29 6:58 dpdklab
2022-05-29 6:55 dpdklab
2022-05-29 5:43 dpdklab
2022-05-29 5:31 dpdklab
2022-05-29 5:12 dpdklab
2022-05-29 5:05 dpdklab
2022-05-28 15:22 dpdklab
2022-05-28 9:51 dpdklab
2022-05-28 7:05 dpdklab
2022-05-28 7:01 dpdklab
2022-05-28 6:17 dpdklab
2022-05-28 5:42 dpdklab
2022-05-28 5:30 dpdklab
2022-05-28 5:11 dpdklab
2022-05-28 5:11 dpdklab
2022-05-28 2:36 dpdklab
2022-05-27 23:51 dpdklab
2022-05-27 10:14 dpdklab
2022-05-27 9:11 dpdklab
2022-05-27 6:25 dpdklab
2022-05-27 5:43 dpdklab
2022-05-27 5:35 dpdklab
2022-05-27 5:31 dpdklab
2022-05-27 5:24 dpdklab
2022-05-27 5:11 dpdklab
2022-05-27 5:09 dpdklab
2022-05-26 10:18 dpdklab
2022-05-26 8:06 dpdklab
2022-05-26 5:42 dpdklab
2022-05-26 5:33 dpdklab
2022-05-26 5:30 dpdklab
2022-05-26 5:17 dpdklab
2022-05-26 5:10 dpdklab
2022-05-26 3:31 dpdklab
2022-05-25 22:51 dpdklab
2022-05-25 8:09 dpdklab
2022-05-25 6:15 dpdklab
2022-05-25 6:15 dpdklab
2022-05-25 5:42 dpdklab
2022-05-25 5:34 dpdklab
2022-05-25 5:29 dpdklab
2022-05-25 5:21 dpdklab
2022-05-25 5:10 dpdklab
2022-05-25 5:10 dpdklab
2022-05-24 13:12 dpdklab
2022-05-24 10:28 dpdklab
2022-05-24 7:53 dpdklab
2022-05-24 6:19 dpdklab
2022-05-24 6:18 dpdklab
2022-05-24 5:42 dpdklab
2022-05-24 5:33 dpdklab
2022-05-24 5:30 dpdklab
2022-05-24 5:21 dpdklab
2022-05-24 5:10 dpdklab
2022-05-24 5:08 dpdklab
2022-05-23 7:17 dpdklab
2022-05-23 7:02 dpdklab
2022-05-23 7:02 dpdklab
2022-05-23 6:38 dpdklab
2022-05-23 6:06 dpdklab
2022-05-23 5:42 dpdklab
2022-05-23 5:36 dpdklab
2022-05-23 5:22 dpdklab
2022-05-23 5:19 dpdklab
2022-05-23 5:10 dpdklab
2022-05-22 7:25 dpdklab
2022-05-22 6:55 dpdklab
2022-05-22 6:53 dpdklab
2022-05-22 6:41 dpdklab
2022-05-22 6:40 dpdklab
2022-05-22 5:41 dpdklab
2022-05-22 5:33 dpdklab
2022-05-22 5:22 dpdklab
2022-05-22 5:21 dpdklab
2022-05-22 5:09 dpdklab
2022-05-21 7:33 dpdklab
2022-05-21 7:10 dpdklab
2022-05-21 7:04 dpdklab
2022-05-21 6:50 dpdklab
2022-05-21 6:44 dpdklab
2022-05-21 5:41 dpdklab
2022-05-21 5:33 dpdklab
2022-05-21 5:29 dpdklab
2022-05-21 5:18 dpdklab
2022-05-21 5:02 dpdklab
2022-05-20 16:04 dpdklab
2022-05-20 12:47 dpdklab
2022-05-20 11:37 dpdklab
2022-05-20 9:39 dpdklab
2022-05-20 8:45 dpdklab
2022-05-20 7:26 dpdklab
2022-05-20 6:10 dpdklab
2022-05-20 6:00 dpdklab
2022-05-20 5:59 dpdklab
2022-05-20 5:58 dpdklab
2022-05-20 5:47 dpdklab
2022-05-20 5:17 dpdklab
2022-05-20 4:42 dpdklab
2022-05-20 3:24 dpdklab
2022-05-20 3:21 dpdklab
2022-05-20 3:21 dpdklab
2022-05-20 3:19 dpdklab
2022-05-20 3:04 dpdklab
2022-05-20 3:04 dpdklab
2022-05-20 3:03 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=20220526050851.5012D600A8@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).