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