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] 2a55c38e277bb795f394d64f679d50c9b6d2cc52
Date: Thu, 18 Aug 2022 05:20:29 +0000 (UTC) [thread overview]
Message-ID: <20220818052029.249266043F@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 1574 bytes --]
_Performance Testing PASS_
Branch: tags/v21.11
2a55c38e277bb795f394d64f679d50c9b6d2cc52 --> 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 | 1.2% |
+----------+-------------+---------+------------+------------------------------+
| 1 | 2 | 2048 | 64 | 1.2% |
+----------+-------------+---------+------------+------------------------------+
| 1 | 1 | 512 | 64 | -3.6% |
+----------+-------------+---------+------------+------------------------------+
| 1 | 1 | 2048 | 64 | -0.1% |
+----------+-------------+---------+------------+------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/21064/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2022-08-18 5:20 UTC|newest]
Thread overview: 81+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-18 5:20 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-08-25 6:26 dpdklab
2022-08-25 6:25 dpdklab
2022-08-25 6:08 dpdklab
2022-08-25 5:43 dpdklab
2022-08-25 5:34 dpdklab
2022-08-25 5:28 dpdklab
2022-08-25 5:20 dpdklab
2022-08-25 5:12 dpdklab
2022-08-25 5:07 dpdklab
2022-08-24 6:19 dpdklab
2022-08-24 5:40 dpdklab
2022-08-24 5:35 dpdklab
2022-08-24 5:32 dpdklab
2022-08-24 5:30 dpdklab
2022-08-24 5:27 dpdklab
2022-08-24 5:26 dpdklab
2022-08-24 5:18 dpdklab
2022-08-24 5:09 dpdklab
2022-08-24 5:05 dpdklab
2022-08-23 5:42 dpdklab
2022-08-23 5:41 dpdklab
2022-08-23 5:31 dpdklab
2022-08-23 5:29 dpdklab
2022-08-23 5:26 dpdklab
2022-08-23 5:18 dpdklab
2022-08-23 5:14 dpdklab
2022-08-23 5:05 dpdklab
2022-08-22 5:53 dpdklab
2022-08-22 5:44 dpdklab
2022-08-22 5:38 dpdklab
2022-08-22 5:34 dpdklab
2022-08-22 5:30 dpdklab
2022-08-22 5:20 dpdklab
2022-08-22 5:10 dpdklab
2022-08-22 5:07 dpdklab
2022-08-21 5:40 dpdklab
2022-08-21 5:38 dpdklab
2022-08-21 5:32 dpdklab
2022-08-21 5:31 dpdklab
2022-08-21 5:28 dpdklab
2022-08-21 5:21 dpdklab
2022-08-21 5:13 dpdklab
2022-08-21 5:07 dpdklab
2022-08-20 5:41 dpdklab
2022-08-20 5:36 dpdklab
2022-08-20 5:32 dpdklab
2022-08-20 5:26 dpdklab
2022-08-20 5:23 dpdklab
2022-08-20 5:18 dpdklab
2022-08-20 5:10 dpdklab
2022-08-20 5:05 dpdklab
2022-08-19 5:40 dpdklab
2022-08-19 5:37 dpdklab
2022-08-19 5:32 dpdklab
2022-08-19 5:26 dpdklab
2022-08-19 5:26 dpdklab
2022-08-19 5:24 dpdklab
2022-08-19 5:23 dpdklab
2022-08-19 5:16 dpdklab
2022-08-19 5:09 dpdklab
2022-08-19 5:07 dpdklab
2022-08-18 5:41 dpdklab
2022-08-18 5:37 dpdklab
2022-08-18 5:36 dpdklab
2022-08-18 5:34 dpdklab
2022-08-18 5:31 dpdklab
2022-08-18 5:29 dpdklab
2022-08-18 5:29 dpdklab
2022-08-18 5:10 dpdklab
2022-08-18 5:07 dpdklab
2022-08-18 3:33 dpdklab
2022-08-18 3:25 dpdklab
2022-08-18 3:23 dpdklab
2022-08-18 3:22 dpdklab
2022-08-18 3:15 dpdklab
2022-08-18 3:13 dpdklab
2022-08-18 3:10 dpdklab
2022-08-18 3:03 dpdklab
2022-08-18 3:00 dpdklab
2022-08-18 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=20220818052029.249266043F@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).