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] bd9e9d22ef03928bde6f7887172359953dfc0432
Date: Wed, 30 Nov 2022 04:04:58 +0000 (UTC) [thread overview]
Message-ID: <20221130040458.5428D60209@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 1574 bytes --]
_Performance Testing PASS_
Branch: tags/v21.11
bd9e9d22ef03928bde6f7887172359953dfc0432 --> 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 XL710-QDA2 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/4
Detail performance results:
+----------+-------------+---------+------------+------------------------------+
| num_cpus | num_threads | txd/rxd | frame_size | throughput difference from |
| | | | | expected |
+==========+=============+=========+============+==============================+
| 1 | 2 | 512 | 64 | 0.4% |
+----------+-------------+---------+------------+------------------------------+
| 1 | 2 | 2048 | 64 | 0.8% |
+----------+-------------+---------+------------+------------------------------+
| 1 | 1 | 512 | 64 | 1.5% |
+----------+-------------+---------+------------+------------------------------+
| 1 | 1 | 2048 | 64 | 0.8% |
+----------+-------------+---------+------------+------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/22473/
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-30 4:05 UTC|newest]
Thread overview: 135+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-30 4:04 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-12-03 19:52 dpdklab
2022-12-03 12:00 dpdklab
2022-12-03 8:05 dpdklab
2022-12-03 8:05 dpdklab
2022-12-03 8:05 dpdklab
2022-12-03 8:04 dpdklab
2022-12-03 8:04 dpdklab
2022-12-03 8:04 dpdklab
2022-12-03 8:04 dpdklab
2022-12-03 8:04 dpdklab
2022-12-03 8:03 dpdklab
2022-12-03 0:01 dpdklab
2022-12-03 0:01 dpdklab
2022-12-02 23:58 dpdklab
2022-12-02 23:58 dpdklab
2022-12-02 23:58 dpdklab
2022-12-02 23:58 dpdklab
2022-12-02 22:49 dpdklab
2022-12-02 18:59 dpdklab
2022-12-02 17:54 dpdklab
2022-12-02 7:35 dpdklab
2022-12-02 6:44 dpdklab
2022-12-02 6:33 dpdklab
2022-12-02 6:31 dpdklab
2022-12-02 6:23 dpdklab
2022-12-02 6:21 dpdklab
2022-12-02 6:07 dpdklab
2022-12-02 6:06 dpdklab
2022-12-01 14:38 dpdklab
2022-12-01 14:38 dpdklab
2022-12-01 14:17 dpdklab
2022-12-01 13:55 dpdklab
2022-12-01 13:36 dpdklab
2022-12-01 13:24 dpdklab
2022-12-01 13:17 dpdklab
2022-12-01 13:10 dpdklab
2022-12-01 12:58 dpdklab
2022-12-01 12:47 dpdklab
2022-12-01 11:52 dpdklab
2022-12-01 11:34 dpdklab
2022-12-01 11:17 dpdklab
2022-12-01 11:16 dpdklab
2022-12-01 10:59 dpdklab
2022-12-01 10:48 dpdklab
2022-12-01 10:25 dpdklab
2022-12-01 10:09 dpdklab
2022-12-01 9:50 dpdklab
2022-12-01 9:30 dpdklab
2022-12-01 9:16 dpdklab
2022-12-01 8:16 dpdklab
2022-12-01 7:55 dpdklab
2022-12-01 7:53 dpdklab
2022-12-01 7:49 dpdklab
2022-12-01 7:28 dpdklab
2022-12-01 7:28 dpdklab
2022-12-01 7:26 dpdklab
2022-12-01 7:17 dpdklab
2022-12-01 7:05 dpdklab
2022-12-01 6:53 dpdklab
2022-12-01 6:44 dpdklab
2022-12-01 6:44 dpdklab
2022-12-01 6:34 dpdklab
2022-12-01 6:32 dpdklab
2022-12-01 6:31 dpdklab
2022-12-01 6:20 dpdklab
2022-12-01 6:07 dpdklab
2022-12-01 6:06 dpdklab
2022-12-01 5:54 dpdklab
2022-12-01 5:46 dpdklab
2022-12-01 5:24 dpdklab
2022-12-01 5:13 dpdklab
2022-12-01 5:03 dpdklab
2022-12-01 4:39 dpdklab
2022-12-01 1:56 dpdklab
2022-12-01 1:45 dpdklab
2022-12-01 1:24 dpdklab
2022-12-01 1:13 dpdklab
2022-12-01 1:03 dpdklab
2022-12-01 0:40 dpdklab
2022-11-30 22:08 dpdklab
2022-11-30 22:01 dpdklab
2022-11-30 20:31 dpdklab
2022-11-30 6:57 dpdklab
2022-11-30 6:40 dpdklab
2022-11-30 6:33 dpdklab
2022-11-30 6:32 dpdklab
2022-11-30 6:28 dpdklab
2022-11-30 6:20 dpdklab
2022-11-30 6:11 dpdklab
2022-11-30 6:06 dpdklab
2022-11-30 5:03 dpdklab
2022-11-30 4:21 dpdklab
2022-11-30 4:17 dpdklab
2022-11-30 4:10 dpdklab
2022-11-30 4:02 dpdklab
2022-11-30 4:01 dpdklab
2022-11-30 3:56 dpdklab
2022-11-29 3:18 dpdklab
2022-11-29 2:52 dpdklab
2022-11-29 2:52 dpdklab
2022-11-29 2:30 dpdklab
2022-11-29 2:09 dpdklab
2022-11-29 1:55 dpdklab
2022-11-29 1:35 dpdklab
2022-11-29 1:14 dpdklab
2022-11-29 0:54 dpdklab
2022-11-29 0:33 dpdklab
2022-11-29 0:22 dpdklab
2022-11-29 0:17 dpdklab
2022-11-29 0:12 dpdklab
2022-11-28 23:50 dpdklab
2022-11-28 23:50 dpdklab
2022-11-28 23:25 dpdklab
2022-11-28 23:23 dpdklab
2022-11-28 23:02 dpdklab
2022-11-28 22:40 dpdklab
2022-11-28 22:34 dpdklab
2022-11-28 22:23 dpdklab
2022-11-28 22:11 dpdklab
2022-11-28 21:59 dpdklab
2022-11-28 21:48 dpdklab
2022-11-28 21:46 dpdklab
2022-11-28 21:37 dpdklab
2022-11-25 19:16 dpdklab
2022-11-25 18:28 dpdklab
2022-11-25 18:25 dpdklab
2022-11-25 18:12 dpdklab
2022-11-25 18:08 dpdklab
2022-11-25 18:02 dpdklab
2022-11-25 18:01 dpdklab
2022-11-25 17:53 dpdklab
2022-11-25 17:52 dpdklab
2022-11-25 17:50 dpdklab
2022-11-25 17:47 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=20221130040458.5428D60209@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).