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] a561d44985d3900d505abb6dd23fa861c5e9eab7
Date: Sun, 14 Aug 2022 05:05:25 +0000 (UTC) [thread overview]
Message-ID: <20220814050525.EA2E86043F@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 1855 bytes --]
_Performance Testing PASS_
Branch: tags/v21.11
a561d44985d3900d505abb6dd23fa861c5e9eab7 --> 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.0% |
+------------+---------+----------+-------------+------------------------------+
| 128 | 256 | 1 | 1 | -0.2% |
+------------+---------+----------+-------------+------------------------------+
| 1024 | 256 | 1 | 1 | 0.0% |
+------------+---------+----------+-------------+------------------------------+
| 256 | 256 | 1 | 1 | 0.1% |
+------------+---------+----------+-------------+------------------------------+
| 1518 | 256 | 1 | 1 | -0.2% |
+------------+---------+----------+-------------+------------------------------+
| 512 | 256 | 1 | 1 | 0.3% |
+------------+---------+----------+-------------+------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/20999/
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-14 5:05 UTC|newest]
Thread overview: 66+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-14 5:05 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-08-17 6:29 dpdklab
2022-08-17 5:49 dpdklab
2022-08-17 5:47 dpdklab
2022-08-17 5:45 dpdklab
2022-08-17 5:20 dpdklab
2022-08-17 5:18 dpdklab
2022-08-17 5:03 dpdklab
2022-08-17 5:03 dpdklab
2022-08-17 5:00 dpdklab
2022-08-17 5:00 dpdklab
2022-08-16 8:22 dpdklab
2022-08-16 8:03 dpdklab
2022-08-16 6:41 dpdklab
2022-08-16 5:58 dpdklab
2022-08-16 5:54 dpdklab
2022-08-16 5:45 dpdklab
2022-08-16 5:15 dpdklab
2022-08-16 5:04 dpdklab
2022-08-16 5:00 dpdklab
2022-08-16 4:59 dpdklab
2022-08-15 6:04 dpdklab
2022-08-15 5:38 dpdklab
2022-08-15 5:36 dpdklab
2022-08-15 5:30 dpdklab
2022-08-15 5:26 dpdklab
2022-08-15 5:22 dpdklab
2022-08-15 5:18 dpdklab
2022-08-15 5:13 dpdklab
2022-08-15 5:08 dpdklab
2022-08-15 5:05 dpdklab
2022-08-14 5:38 dpdklab
2022-08-14 5:35 dpdklab
2022-08-14 5:30 dpdklab
2022-08-14 5:29 dpdklab
2022-08-14 5:28 dpdklab
2022-08-14 5:22 dpdklab
2022-08-14 5:19 dpdklab
2022-08-14 5:14 dpdklab
2022-08-14 5:07 dpdklab
2022-08-13 5:44 dpdklab
2022-08-13 5:42 dpdklab
2022-08-13 5:42 dpdklab
2022-08-13 5:38 dpdklab
2022-08-13 5:37 dpdklab
2022-08-13 5:30 dpdklab
2022-08-13 5:19 dpdklab
2022-08-13 5:18 dpdklab
2022-08-13 5:07 dpdklab
2022-08-13 5:05 dpdklab
2022-08-12 6:16 dpdklab
2022-08-12 6:14 dpdklab
2022-08-12 5:40 dpdklab
2022-08-12 5:32 dpdklab
2022-08-12 5:28 dpdklab
2022-08-12 5:16 dpdklab
2022-08-12 5:09 dpdklab
2022-08-12 5:06 dpdklab
2022-08-12 3:27 dpdklab
2022-08-12 3:26 dpdklab
2022-08-12 3:20 dpdklab
2022-08-12 3:16 dpdklab
2022-08-12 3:08 dpdklab
2022-08-12 3:04 dpdklab
2022-08-12 3:01 dpdklab
2022-08-12 2:57 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=20220814050525.EA2E86043F@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).