From: dpdklab@iol.unh.edu
To: 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] 214462a05b8e0cf08bbd06c10441d25baae17137
Date: Thu, 9 Jun 2022 05:31:31 +0000 (UTC) [thread overview]
Message-ID: <20220609053131.214D165DE6@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 1895 bytes --]
_Performance Testing PASS_
Branch: tags/v21.11
214462a05b8e0cf08bbd06c10441d25baae17137 --> performance testing pass
Test environment and result as below:
Ubuntu 20.04
Kernel: 4.15.0-generic
Compiler: gcc 7.4
NIC: Intel Corporation Ethernet Converged Network Adapter 82599ES 10000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/6
Detail performance results:
+----------+-------------+---------+------------+------------------------------+
| num_cpus | num_threads | txd/rxd | frame_size | throughput difference from |
| | | | | expected |
+==========+=============+=========+============+==============================+
| 1 | 2 | 128 | 64 | -0.2% |
+----------+-------------+---------+------------+------------------------------+
| 1 | 2 | 512 | 64 | 0.2% |
+----------+-------------+---------+------------+------------------------------+
| 1 | 2 | 2048 | 64 | -0.2% |
+----------+-------------+---------+------------+------------------------------+
| 1 | 1 | 128 | 64 | -0.4% |
+----------+-------------+---------+------------+------------------------------+
| 1 | 1 | 512 | 64 | 0.2% |
+----------+-------------+---------+------------+------------------------------+
| 1 | 1 | 2048 | 64 | -0.1% |
+----------+-------------+---------+------------+------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/20206/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2022-06-09 5:31 UTC|newest]
Thread overview: 230+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-09 5:31 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-06-26 19:33 dpdklab
2022-06-26 18:41 dpdklab
2022-06-26 16:38 dpdklab
2022-06-25 16:56 dpdklab
2022-06-24 10:45 dpdklab
2022-06-20 5:42 dpdklab
2022-06-20 5:34 dpdklab
2022-06-20 5:31 dpdklab
2022-06-20 5:31 dpdklab
2022-06-20 5:30 dpdklab
2022-06-20 5:29 dpdklab
2022-06-20 5:18 dpdklab
2022-06-20 5:15 dpdklab
2022-06-20 5:10 dpdklab
2022-06-20 5:10 dpdklab
2022-06-19 5:43 dpdklab
2022-06-19 5:35 dpdklab
2022-06-19 5:32 dpdklab
2022-06-19 5:31 dpdklab
2022-06-19 5:30 dpdklab
2022-06-19 5:30 dpdklab
2022-06-19 5:19 dpdklab
2022-06-19 5:16 dpdklab
2022-06-19 5:11 dpdklab
2022-06-19 5:10 dpdklab
2022-06-18 6:18 dpdklab
2022-06-18 5:48 dpdklab
2022-06-18 5:43 dpdklab
2022-06-18 5:42 dpdklab
2022-06-18 5:35 dpdklab
2022-06-18 5:31 dpdklab
2022-06-18 5:23 dpdklab
2022-06-18 5:19 dpdklab
2022-06-18 5:10 dpdklab
2022-06-18 5:08 dpdklab
2022-06-17 6:16 dpdklab
2022-06-17 6:13 dpdklab
2022-06-17 6:12 dpdklab
2022-06-17 6:09 dpdklab
2022-06-17 5:43 dpdklab
2022-06-17 5:35 dpdklab
2022-06-17 5:22 dpdklab
2022-06-17 5:18 dpdklab
2022-06-17 5:10 dpdklab
2022-06-17 5:08 dpdklab
2022-06-16 7:24 dpdklab
2022-06-16 7:08 dpdklab
2022-06-16 7:08 dpdklab
2022-06-16 6:39 dpdklab
2022-06-16 5:42 dpdklab
2022-06-16 5:35 dpdklab
2022-06-16 5:30 dpdklab
2022-06-16 5:23 dpdklab
2022-06-16 5:12 dpdklab
2022-06-16 5:12 dpdklab
2022-06-15 18:01 dpdklab
2022-06-15 6:58 dpdklab
2022-06-15 6:52 dpdklab
2022-06-15 6:51 dpdklab
2022-06-15 6:43 dpdklab
2022-06-15 5:42 dpdklab
2022-06-15 5:34 dpdklab
2022-06-15 5:29 dpdklab
2022-06-15 5:22 dpdklab
2022-06-15 5:12 dpdklab
2022-06-15 5:10 dpdklab
2022-06-14 23:24 dpdklab
2022-06-14 7:17 dpdklab
2022-06-14 7:08 dpdklab
2022-06-14 6:41 dpdklab
2022-06-14 6:31 dpdklab
2022-06-14 5:42 dpdklab
2022-06-14 5:35 dpdklab
2022-06-14 5:29 dpdklab
2022-06-14 5:19 dpdklab
2022-06-14 5:10 dpdklab
2022-06-14 5:10 dpdklab
2022-06-13 15:28 dpdklab
2022-06-13 7:26 dpdklab
2022-06-13 7:10 dpdklab
2022-06-13 6:42 dpdklab
2022-06-13 6:38 dpdklab
2022-06-13 5:57 dpdklab
2022-06-13 5:43 dpdklab
2022-06-13 5:36 dpdklab
2022-06-13 5:23 dpdklab
2022-06-13 5:23 dpdklab
2022-06-13 5:12 dpdklab
2022-06-13 5:12 dpdklab
2022-06-13 3:32 dpdklab
2022-06-12 9:54 dpdklab
2022-06-12 6:35 dpdklab
2022-06-12 6:17 dpdklab
2022-06-12 6:15 dpdklab
2022-06-12 6:11 dpdklab
2022-06-12 5:43 dpdklab
2022-06-12 5:35 dpdklab
2022-06-12 5:30 dpdklab
2022-06-12 5:22 dpdklab
2022-06-12 5:12 dpdklab
2022-06-12 5:11 dpdklab
2022-06-11 13:45 dpdklab
2022-06-11 8:13 dpdklab
2022-06-11 7:14 dpdklab
2022-06-11 6:32 dpdklab
2022-06-11 6:19 dpdklab
2022-06-11 5:43 dpdklab
2022-06-11 5:34 dpdklab
2022-06-11 5:32 dpdklab
2022-06-11 5:18 dpdklab
2022-06-11 5:10 dpdklab
2022-06-11 4:58 dpdklab
2022-06-10 11:16 dpdklab
2022-06-10 7:09 dpdklab
2022-06-10 7:04 dpdklab
2022-06-10 6:58 dpdklab
2022-06-10 6:34 dpdklab
2022-06-10 5:42 dpdklab
2022-06-10 5:35 dpdklab
2022-06-10 5:30 dpdklab
2022-06-10 5:19 dpdklab
2022-06-10 5:13 dpdklab
2022-06-10 5:11 dpdklab
2022-06-09 11:17 dpdklab
2022-06-09 8:54 dpdklab
2022-06-09 8:45 dpdklab
2022-06-09 8:39 dpdklab
2022-06-09 6:04 dpdklab
2022-06-09 5:43 dpdklab
2022-06-09 5:36 dpdklab
2022-06-09 5:20 dpdklab
2022-06-09 5:11 dpdklab
2022-06-09 4:57 dpdklab
2022-06-08 15:44 dpdklab
2022-06-08 7:34 dpdklab
2022-06-08 6:59 dpdklab
2022-06-08 6:52 dpdklab
2022-06-08 6:34 dpdklab
2022-06-08 6:30 dpdklab
2022-06-08 5:42 dpdklab
2022-06-08 5:34 dpdklab
2022-06-08 5:29 dpdklab
2022-06-08 5:18 dpdklab
2022-06-08 5:12 dpdklab
2022-06-08 5:10 dpdklab
2022-06-07 21:41 dpdklab
2022-06-07 7:44 dpdklab
2022-06-07 6:50 dpdklab
2022-06-07 6:49 dpdklab
2022-06-07 6:43 dpdklab
2022-06-07 6:31 dpdklab
2022-06-07 5:42 dpdklab
2022-06-07 5:35 dpdklab
2022-06-07 5:29 dpdklab
2022-06-07 5:19 dpdklab
2022-06-07 5:16 dpdklab
2022-06-07 5:11 dpdklab
2022-06-06 15:00 dpdklab
2022-06-06 9:36 dpdklab
2022-06-06 9:13 dpdklab
2022-06-06 8:56 dpdklab
2022-06-06 6:52 dpdklab
2022-06-06 5:50 dpdklab
2022-06-06 5:43 dpdklab
2022-06-06 5:31 dpdklab
2022-06-06 5:30 dpdklab
2022-06-06 5:13 dpdklab
2022-06-06 5:02 dpdklab
2022-06-06 3:02 dpdklab
2022-06-05 23:42 dpdklab
2022-06-05 7:20 dpdklab
2022-06-05 7:11 dpdklab
2022-06-05 7:11 dpdklab
2022-06-05 7:01 dpdklab
2022-06-05 5:42 dpdklab
2022-06-05 5:34 dpdklab
2022-06-05 5:30 dpdklab
2022-06-05 5:18 dpdklab
2022-06-05 5:11 dpdklab
2022-06-05 5:11 dpdklab
2022-06-04 7:41 dpdklab
2022-06-04 6:54 dpdklab
2022-06-04 6:40 dpdklab
2022-06-04 6:39 dpdklab
2022-06-04 5:41 dpdklab
2022-06-04 5:35 dpdklab
2022-06-04 5:29 dpdklab
2022-06-04 5:18 dpdklab
2022-06-04 5:09 dpdklab
2022-06-04 5:02 dpdklab
2022-06-03 8:34 dpdklab
2022-06-03 7:46 dpdklab
2022-06-03 7:38 dpdklab
2022-06-03 6:53 dpdklab
2022-06-03 5:43 dpdklab
2022-06-03 5:30 dpdklab
2022-06-03 5:18 dpdklab
2022-06-03 5:11 dpdklab
2022-06-03 5:08 dpdklab
2022-06-02 19:13 dpdklab
2022-06-02 9:57 dpdklab
2022-06-02 7:19 dpdklab
2022-06-02 6:47 dpdklab
2022-06-02 5:42 dpdklab
2022-06-02 5:34 dpdklab
2022-06-02 5:30 dpdklab
2022-06-02 5:23 dpdklab
2022-06-02 5:15 dpdklab
2022-06-02 5:11 dpdklab
2022-06-02 4:45 dpdklab
2022-06-01 21:18 dpdklab
2022-06-01 17:21 dpdklab
2022-06-01 17:15 dpdklab
2022-06-01 14:44 dpdklab
2022-06-01 14:28 dpdklab
2022-06-01 12:34 dpdklab
2022-06-01 12:18 dpdklab
2022-06-01 6:06 dpdklab
2022-06-01 5:54 dpdklab
2022-06-01 5:51 dpdklab
2022-06-01 5:45 dpdklab
2022-06-01 5:08 dpdklab
2022-06-01 5:01 dpdklab
2022-06-01 3:54 dpdklab
2022-06-01 3:23 dpdklab
2022-06-01 3:18 dpdklab
2022-06-01 3:11 dpdklab
2022-06-01 3:03 dpdklab
2022-06-01 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=20220609053131.214D165DE6@dpdk-ubuntu.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--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).