From: dpdklab@iol.unh.edu
To: Ajit Khaparde <ajit.khaparde@broadcom.com>,
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] b05d183a7f6040a6748eae5717f030e00e30544c
Date: Wed, 23 Feb 2022 06:03:22 +0000 (UTC) [thread overview]
Message-ID: <20220223060322.E8E60601B6@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 1576 bytes --]
_Performance Testing PASS_
Branch: tags/v20.11
b05d183a7f6040a6748eae5717f030e00e30544c --> performance testing pass
Test environment and result as below:
Ubuntu 20.04
Kernel: 4.15.0-65-generic
Compiler: gcc gcc (Ubuntu 7.4.0-1ubuntu1~18.04.1) 7.4.0
NIC: Broadcom Inc. brcm_57414 25000 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.2% |
+----------+-------------+---------+------------+------------------------------+
| 1 | 2 | 2048 | 64 | -0.1% |
+----------+-------------+---------+------------+------------------------------+
| 1 | 1 | 512 | 64 | -0.2% |
+----------+-------------+---------+------------+------------------------------+
| 1 | 1 | 2048 | 64 | -0.1% |
+----------+-------------+---------+------------+------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/18852/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2022-02-23 6:03 UTC|newest]
Thread overview: 411+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-23 6:03 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-02-23 20:45 dpdklab
2022-02-23 14:09 dpdklab
2022-02-23 12:04 dpdklab
2022-02-23 11:03 dpdklab
2022-02-23 7:44 dpdklab
2022-02-23 6:05 dpdklab
2022-02-23 6:01 dpdklab
2022-02-23 5:57 dpdklab
2022-02-23 5:56 dpdklab
2022-02-23 5:52 dpdklab
2022-02-23 5:49 dpdklab
2022-02-23 5:48 dpdklab
2022-02-23 5:48 dpdklab
2022-02-22 13:05 dpdklab
2022-02-22 10:10 dpdklab
2022-02-22 9:19 dpdklab
2022-02-22 9:18 dpdklab
2022-02-22 8:10 dpdklab
2022-02-22 6:05 dpdklab
2022-02-22 6:01 dpdklab
2022-02-22 6:00 dpdklab
2022-02-22 5:55 dpdklab
2022-02-22 5:53 dpdklab
2022-02-22 5:49 dpdklab
2022-02-22 5:47 dpdklab
2022-02-22 5:46 dpdklab
2022-02-21 7:41 dpdklab
2022-02-21 7:40 dpdklab
2022-02-21 7:30 dpdklab
2022-02-21 7:01 dpdklab
2022-02-21 6:09 dpdklab
2022-02-21 6:04 dpdklab
2022-02-21 6:02 dpdklab
2022-02-21 6:01 dpdklab
2022-02-21 5:59 dpdklab
2022-02-21 5:56 dpdklab
2022-02-21 5:49 dpdklab
2022-02-21 5:49 dpdklab
2022-02-21 5:47 dpdklab
2022-02-20 10:43 dpdklab
2022-02-20 9:16 dpdklab
2022-02-20 7:06 dpdklab
2022-02-20 6:57 dpdklab
2022-02-20 6:08 dpdklab
2022-02-20 6:05 dpdklab
2022-02-20 6:01 dpdklab
2022-02-20 6:01 dpdklab
2022-02-20 6:00 dpdklab
2022-02-20 5:57 dpdklab
2022-02-20 5:50 dpdklab
2022-02-20 5:49 dpdklab
2022-02-20 5:48 dpdklab
2022-02-19 22:14 dpdklab
2022-02-19 11:32 dpdklab
2022-02-19 9:13 dpdklab
2022-02-19 7:51 dpdklab
2022-02-19 6:10 dpdklab
2022-02-19 6:06 dpdklab
2022-02-19 6:00 dpdklab
2022-02-19 6:00 dpdklab
2022-02-19 5:56 dpdklab
2022-02-19 5:53 dpdklab
2022-02-19 5:51 dpdklab
2022-02-18 9:48 dpdklab
2022-02-18 7:33 dpdklab
2022-02-18 7:24 dpdklab
2022-02-18 6:12 dpdklab
2022-02-18 6:09 dpdklab
2022-02-18 6:04 dpdklab
2022-02-18 6:00 dpdklab
2022-02-18 6:00 dpdklab
2022-02-18 5:59 dpdklab
2022-02-18 5:54 dpdklab
2022-02-18 5:49 dpdklab
2022-02-18 5:48 dpdklab
2022-02-18 5:46 dpdklab
2022-02-17 9:38 dpdklab
2022-02-17 7:31 dpdklab
2022-02-17 6:40 dpdklab
2022-02-17 6:09 dpdklab
2022-02-17 6:08 dpdklab
2022-02-17 6:03 dpdklab
2022-02-17 5:59 dpdklab
2022-02-17 5:58 dpdklab
2022-02-17 5:58 dpdklab
2022-02-17 5:55 dpdklab
2022-02-17 5:54 dpdklab
2022-02-17 5:51 dpdklab
2022-02-17 5:49 dpdklab
2022-02-17 3:51 dpdklab
2022-02-16 13:25 dpdklab
2022-02-16 8:51 dpdklab
2022-02-16 8:39 dpdklab
2022-02-16 7:50 dpdklab
2022-02-16 6:09 dpdklab
2022-02-16 6:04 dpdklab
2022-02-16 6:00 dpdklab
2022-02-16 5:59 dpdklab
2022-02-16 5:59 dpdklab
2022-02-16 5:54 dpdklab
2022-02-16 5:49 dpdklab
2022-02-16 5:48 dpdklab
2022-02-16 5:45 dpdklab
2022-02-15 15:56 dpdklab
2022-02-15 9:49 dpdklab
2022-02-15 9:05 dpdklab
2022-02-15 7:47 dpdklab
2022-02-15 6:11 dpdklab
2022-02-15 6:10 dpdklab
2022-02-15 6:06 dpdklab
2022-02-15 6:00 dpdklab
2022-02-15 5:59 dpdklab
2022-02-15 5:55 dpdklab
2022-02-15 5:54 dpdklab
2022-02-15 5:49 dpdklab
2022-02-15 5:49 dpdklab
2022-02-14 10:40 dpdklab
2022-02-14 10:40 dpdklab
2022-02-14 8:24 dpdklab
2022-02-14 7:32 dpdklab
2022-02-14 6:04 dpdklab
2022-02-14 6:01 dpdklab
2022-02-14 6:00 dpdklab
2022-02-14 5:59 dpdklab
2022-02-14 5:55 dpdklab
2022-02-14 5:54 dpdklab
2022-02-14 5:50 dpdklab
2022-02-14 5:49 dpdklab
2022-02-14 5:47 dpdklab
2022-02-13 19:36 dpdklab
2022-02-13 9:27 dpdklab
2022-02-13 9:27 dpdklab
2022-02-13 6:31 dpdklab
2022-02-13 6:18 dpdklab
2022-02-13 6:03 dpdklab
2022-02-13 6:00 dpdklab
2022-02-13 5:59 dpdklab
2022-02-13 5:58 dpdklab
2022-02-13 5:54 dpdklab
2022-02-13 5:53 dpdklab
2022-02-13 5:49 dpdklab
2022-02-13 5:48 dpdklab
2022-02-13 5:46 dpdklab
2022-02-12 22:15 dpdklab
2022-02-12 9:42 dpdklab
2022-02-12 9:42 dpdklab
2022-02-12 9:36 dpdklab
2022-02-12 6:35 dpdklab
2022-02-12 6:03 dpdklab
2022-02-12 6:00 dpdklab
2022-02-12 6:00 dpdklab
2022-02-12 5:58 dpdklab
2022-02-12 5:54 dpdklab
2022-02-12 5:54 dpdklab
2022-02-12 5:49 dpdklab
2022-02-12 5:48 dpdklab
2022-02-12 5:46 dpdklab
2022-02-11 17:14 dpdklab
2022-02-11 13:37 dpdklab
2022-02-11 10:56 dpdklab
2022-02-11 6:08 dpdklab
2022-02-11 6:03 dpdklab
2022-02-11 6:00 dpdklab
2022-02-11 5:59 dpdklab
2022-02-11 5:58 dpdklab
2022-02-11 5:54 dpdklab
2022-02-11 5:49 dpdklab
2022-02-11 5:48 dpdklab
2022-02-11 5:45 dpdklab
2022-02-11 1:10 dpdklab
2022-02-10 22:47 dpdklab
2022-02-10 20:07 dpdklab
2022-02-10 6:30 dpdklab
2022-02-10 6:14 dpdklab
2022-02-10 6:13 dpdklab
2022-02-10 6:12 dpdklab
2022-02-10 6:11 dpdklab
2022-02-10 6:07 dpdklab
2022-02-10 6:03 dpdklab
2022-02-10 6:01 dpdklab
2022-02-10 5:55 dpdklab
2022-02-09 13:18 dpdklab
2022-02-09 13:18 dpdklab
2022-02-09 11:34 dpdklab
2022-02-09 10:21 dpdklab
2022-02-09 6:08 dpdklab
2022-02-09 6:07 dpdklab
2022-02-09 6:01 dpdklab
2022-02-09 6:01 dpdklab
2022-02-09 5:56 dpdklab
2022-02-09 5:55 dpdklab
2022-02-09 5:53 dpdklab
2022-02-09 5:51 dpdklab
2022-02-09 5:49 dpdklab
2022-02-08 10:33 dpdklab
2022-02-08 10:08 dpdklab
2022-02-08 9:59 dpdklab
2022-02-08 6:36 dpdklab
2022-02-08 6:08 dpdklab
2022-02-08 6:03 dpdklab
2022-02-08 6:00 dpdklab
2022-02-08 5:59 dpdklab
2022-02-08 5:55 dpdklab
2022-02-08 5:54 dpdklab
2022-02-08 5:52 dpdklab
2022-02-08 5:48 dpdklab
2022-02-08 5:46 dpdklab
2022-02-07 11:37 dpdklab
2022-02-07 10:35 dpdklab
2022-02-07 6:37 dpdklab
2022-02-07 6:16 dpdklab
2022-02-07 6:07 dpdklab
2022-02-07 6:03 dpdklab
2022-02-07 6:00 dpdklab
2022-02-07 5:58 dpdklab
2022-02-07 5:54 dpdklab
2022-02-07 5:52 dpdklab
2022-02-07 5:49 dpdklab
2022-02-07 5:46 dpdklab
2022-02-07 5:45 dpdklab
2022-02-06 10:50 dpdklab
2022-02-06 10:20 dpdklab
2022-02-06 6:50 dpdklab
2022-02-06 6:26 dpdklab
2022-02-06 6:10 dpdklab
2022-02-06 6:04 dpdklab
2022-02-06 6:00 dpdklab
2022-02-06 5:59 dpdklab
2022-02-06 5:59 dpdklab
2022-02-06 5:55 dpdklab
2022-02-06 5:54 dpdklab
2022-02-06 5:51 dpdklab
2022-02-06 5:50 dpdklab
2022-02-05 10:35 dpdklab
2022-02-05 9:44 dpdklab
2022-02-05 6:39 dpdklab
2022-02-05 6:25 dpdklab
2022-02-05 6:06 dpdklab
2022-02-05 6:02 dpdklab
2022-02-05 5:59 dpdklab
2022-02-05 5:58 dpdklab
2022-02-05 5:53 dpdklab
2022-02-05 5:53 dpdklab
2022-02-05 5:51 dpdklab
2022-02-05 5:47 dpdklab
2022-02-05 5:45 dpdklab
2022-02-04 8:14 dpdklab
2022-02-04 6:46 dpdklab
2022-02-04 6:42 dpdklab
2022-02-04 6:17 dpdklab
2022-02-04 6:02 dpdklab
2022-02-04 6:01 dpdklab
2022-02-04 5:59 dpdklab
2022-02-04 5:58 dpdklab
2022-02-04 5:57 dpdklab
2022-02-04 5:54 dpdklab
2022-02-04 5:54 dpdklab
2022-02-04 5:53 dpdklab
2022-02-04 5:51 dpdklab
2022-02-04 5:48 dpdklab
2022-02-04 0:41 dpdklab
2022-02-04 0:30 dpdklab
2022-02-03 21:15 dpdklab
2022-02-03 8:55 dpdklab
2022-02-03 6:51 dpdklab
2022-02-03 6:48 dpdklab
2022-02-03 6:28 dpdklab
2022-02-03 6:13 dpdklab
2022-02-03 5:59 dpdklab
2022-02-03 5:56 dpdklab
2022-02-03 5:47 dpdklab
2022-02-02 8:37 dpdklab
2022-02-02 7:07 dpdklab
2022-02-02 6:26 dpdklab
2022-02-02 6:12 dpdklab
2022-02-02 6:03 dpdklab
2022-02-02 5:59 dpdklab
2022-02-02 5:54 dpdklab
2022-02-02 5:53 dpdklab
2022-02-02 5:52 dpdklab
2022-02-02 5:47 dpdklab
2022-02-02 5:46 dpdklab
2022-02-01 8:20 dpdklab
2022-02-01 7:06 dpdklab
2022-02-01 6:37 dpdklab
2022-02-01 6:24 dpdklab
2022-02-01 6:13 dpdklab
2022-02-01 6:00 dpdklab
2022-02-01 5:59 dpdklab
2022-02-01 5:55 dpdklab
2022-02-01 5:54 dpdklab
2022-02-01 5:52 dpdklab
2022-02-01 5:49 dpdklab
2022-02-01 5:46 dpdklab
2022-02-01 0:00 dpdklab
2022-01-31 23:36 dpdklab
2022-01-31 23:01 dpdklab
2022-01-31 21:39 dpdklab
2022-01-31 7:00 dpdklab
2022-01-31 6:46 dpdklab
2022-01-31 6:40 dpdklab
2022-01-31 6:30 dpdklab
2022-01-31 6:11 dpdklab
2022-01-31 6:08 dpdklab
2022-01-31 6:00 dpdklab
2022-01-31 5:54 dpdklab
2022-01-31 5:52 dpdklab
2022-01-31 5:49 dpdklab
2022-01-31 5:47 dpdklab
2022-01-30 8:41 dpdklab
2022-01-30 7:08 dpdklab
2022-01-30 6:37 dpdklab
2022-01-30 6:20 dpdklab
2022-01-30 6:11 dpdklab
2022-01-30 6:00 dpdklab
2022-01-30 5:56 dpdklab
2022-01-30 5:54 dpdklab
2022-01-30 5:52 dpdklab
2022-01-30 5:49 dpdklab
2022-01-30 5:47 dpdklab
2022-01-29 8:35 dpdklab
2022-01-29 6:53 dpdklab
2022-01-29 6:47 dpdklab
2022-01-29 6:18 dpdklab
2022-01-29 6:12 dpdklab
2022-01-29 6:08 dpdklab
2022-01-29 5:59 dpdklab
2022-01-29 5:53 dpdklab
2022-01-29 5:51 dpdklab
2022-01-29 5:48 dpdklab
2022-01-29 5:45 dpdklab
2022-01-28 16:26 dpdklab
2022-01-28 7:04 dpdklab
2022-01-28 6:43 dpdklab
2022-01-28 6:40 dpdklab
2022-01-28 6:35 dpdklab
2022-01-28 6:16 dpdklab
2022-01-28 6:04 dpdklab
2022-01-28 5:59 dpdklab
2022-01-28 5:56 dpdklab
2022-01-28 5:53 dpdklab
2022-01-28 5:51 dpdklab
2022-01-27 16:36 dpdklab
2022-01-27 8:22 dpdklab
2022-01-27 6:56 dpdklab
2022-01-27 6:41 dpdklab
2022-01-27 6:02 dpdklab
2022-01-27 5:55 dpdklab
2022-01-27 5:54 dpdklab
2022-01-27 5:51 dpdklab
2022-01-26 21:11 dpdklab
2022-01-26 7:00 dpdklab
2022-01-26 6:42 dpdklab
2022-01-26 6:37 dpdklab
2022-01-26 6:24 dpdklab
2022-01-26 6:19 dpdklab
2022-01-26 6:18 dpdklab
2022-01-26 6:16 dpdklab
2022-01-26 6:13 dpdklab
2022-01-26 6:10 dpdklab
2022-01-26 3:46 dpdklab
2022-01-26 3:32 dpdklab
2022-01-25 6:08 dpdklab
2022-01-25 6:05 dpdklab
2022-01-25 6:02 dpdklab
2022-01-25 6:00 dpdklab
2022-01-25 5:58 dpdklab
2022-01-25 5:57 dpdklab
2022-01-25 5:54 dpdklab
2022-01-25 5:54 dpdklab
2022-01-25 5:53 dpdklab
2022-01-24 8:43 dpdklab
2022-01-24 6:43 dpdklab
2022-01-24 6:26 dpdklab
2022-01-24 6:21 dpdklab
2022-01-24 6:10 dpdklab
2022-01-24 6:03 dpdklab
2022-01-24 6:00 dpdklab
2022-01-24 5:59 dpdklab
2022-01-24 5:59 dpdklab
2022-01-24 5:55 dpdklab
2022-01-24 5:55 dpdklab
2022-01-24 5:52 dpdklab
2022-01-24 5:52 dpdklab
2022-01-23 8:29 dpdklab
2022-01-23 6:54 dpdklab
2022-01-23 6:44 dpdklab
2022-01-23 6:20 dpdklab
2022-01-23 6:10 dpdklab
2022-01-23 6:02 dpdklab
2022-01-23 6:00 dpdklab
2022-01-23 5:59 dpdklab
2022-01-23 5:58 dpdklab
2022-01-23 5:58 dpdklab
2022-01-23 5:54 dpdklab
2022-01-23 5:54 dpdklab
2022-01-23 5:51 dpdklab
2022-01-23 5:49 dpdklab
2022-01-22 8:46 dpdklab
2022-01-22 6:33 dpdklab
2022-01-22 6:18 dpdklab
2022-01-22 6:10 dpdklab
2022-01-22 6:03 dpdklab
2022-01-22 6:00 dpdklab
2022-01-22 5:59 dpdklab
2022-01-22 5:55 dpdklab
2022-01-22 5:54 dpdklab
2022-01-22 5:52 dpdklab
2022-01-22 5:51 dpdklab
2022-01-22 5:46 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=20220223060322.E8E60601B6@dpdk-ubuntu.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=ajit.khaparde@broadcom.com \
--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).