automatic DPDK test reports
 help / color / mirror / Atom feed
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] 155acf8e9da0e259524cbd7ee5c32d263740de3d
Date: Wed, 26 Jul 2023 20:08:37 -0700 (PDT)	[thread overview]
Message-ID: <64c1dfb5.050a0220.a6114.0e38SMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Performance Testing PASS_

Branch: tags/v21.11

155acf8e9da0e259524cbd7ee5c32d263740de3d --> performance testing pass

Test environment and result as below:

Ubuntu 20.04 ARM
Kernel: 5.11.0-46-generic
Compiler: gcc 9.4.0
NIC: Arm Broadcom Inc. brcm_57414 25000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/2

Detail performance results: 
+------------+---------+----------+-------------+------------------------------+
| frame_size | txd/rxd | num_cpus | num_threads |  throughput difference from  |
|            |         |          |             |           expected           |
+============+=========+==========+=============+==============================+
| 64         | 512     | 1        | 1           | -0.3%                        |
+------------+---------+----------+-------------+------------------------------+
| 64         | 2048    | 1        | 1           | -0.7%                        |
+------------+---------+----------+-------------+------------------------------+

Ubuntu 22.04
Kernel: 5.15.0-39-generic
Compiler: gcc gcc (Ubuntu 11.2.0-19ubuntu1) 11.2.0
NIC: Broadcom Inc. and subsidiaries BCM57414 NetXtreme-E 10Gb/25Gb RDMA Ethernet Controller 16d7 25 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/3

Detail performance results: 
+------------+---------+----------+-------------+------------------------------+
| frame_size | txd/rxd | num_cpus | num_threads |  throughput difference from  |
|            |         |          |             |           expected           |
+============+=========+==========+=============+==============================+
| 64         | 128     | 1        | 1           | -0.1%                        |
+------------+---------+----------+-------------+------------------------------+
| 64         | 512     | 1        | 1           | -0.0%                        |
+------------+---------+----------+-------------+------------------------------+
| 64         | 2048    | 1        | 1           | -0.0%                        |
+------------+---------+----------+-------------+------------------------------+

To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/25611/

UNH-IOL DPDK Community Lab

To manage your email subscriptions, visit: 
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/

             reply	other threads:[~2023-07-27  3:08 UTC|newest]

Thread overview: 209+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-27  3:08 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-08-02  8:13 dpdklab
2023-08-02  7:54 dpdklab
2023-08-02  7:48 dpdklab
2023-08-02  7:42 dpdklab
2023-08-02  7:27 dpdklab
2023-08-02  7:05 dpdklab
2023-08-02  6:58 dpdklab
2023-08-02  6:33 dpdklab
2023-08-02  6:33 dpdklab
2023-08-02  6:32 dpdklab
2023-08-02  6:31 dpdklab
2023-08-02  6:31 dpdklab
2023-08-02  6:19 dpdklab
2023-08-02  6:14 dpdklab
2023-08-02  6:14 dpdklab
2023-08-02  6:09 dpdklab
2023-08-02  5:26 dpdklab
2023-08-02  5:21 dpdklab
2023-08-02  5:13 dpdklab
2023-08-02  5:10 dpdklab
2023-08-02  5:08 dpdklab
2023-08-02  5:06 dpdklab
2023-08-02  5:04 dpdklab
2023-08-02  5:03 dpdklab
2023-08-02  5:03 dpdklab
2023-08-02  5:02 dpdklab
2023-08-01  8:07 dpdklab
2023-08-01  7:12 dpdklab
2023-08-01  7:08 dpdklab
2023-08-01  7:05 dpdklab
2023-08-01  7:01 dpdklab
2023-08-01  6:41 dpdklab
2023-08-01  6:36 dpdklab
2023-08-01  6:34 dpdklab
2023-08-01  6:21 dpdklab
2023-08-01  6:12 dpdklab
2023-08-01  6:10 dpdklab
2023-08-01  6:06 dpdklab
2023-08-01  6:00 dpdklab
2023-08-01  5:49 dpdklab
2023-08-01  5:44 dpdklab
2023-08-01  5:43 dpdklab
2023-08-01  5:36 dpdklab
2023-08-01  5:36 dpdklab
2023-08-01  5:28 dpdklab
2023-08-01  5:16 dpdklab
2023-08-01  5:13 dpdklab
2023-08-01  5:13 dpdklab
2023-08-01  5:12 dpdklab
2023-08-01  5:10 dpdklab
2023-08-01  5:09 dpdklab
2023-08-01  5:09 dpdklab
2023-07-31  8:00 dpdklab
2023-07-31  7:53 dpdklab
2023-07-31  7:33 dpdklab
2023-07-31  7:07 dpdklab
2023-07-31  6:48 dpdklab
2023-07-31  6:23 dpdklab
2023-07-31  6:19 dpdklab
2023-07-31  6:17 dpdklab
2023-07-31  6:17 dpdklab
2023-07-31  6:11 dpdklab
2023-07-31  6:10 dpdklab
2023-07-31  6:07 dpdklab
2023-07-31  6:06 dpdklab
2023-07-31  6:05 dpdklab
2023-07-31  6:04 dpdklab
2023-07-31  6:04 dpdklab
2023-07-31  5:58 dpdklab
2023-07-31  5:46 dpdklab
2023-07-31  5:33 dpdklab
2023-07-31  5:27 dpdklab
2023-07-31  5:14 dpdklab
2023-07-31  5:11 dpdklab
2023-07-31  5:09 dpdklab
2023-07-31  5:09 dpdklab
2023-07-31  5:06 dpdklab
2023-07-31  5:05 dpdklab
2023-07-31  5:05 dpdklab
2023-07-30  7:07 dpdklab
2023-07-30  6:45 dpdklab
2023-07-30  6:38 dpdklab
2023-07-30  6:25 dpdklab
2023-07-30  6:21 dpdklab
2023-07-30  6:15 dpdklab
2023-07-30  6:12 dpdklab
2023-07-30  6:11 dpdklab
2023-07-30  6:06 dpdklab
2023-07-30  6:06 dpdklab
2023-07-30  6:06 dpdklab
2023-07-30  6:03 dpdklab
2023-07-30  5:59 dpdklab
2023-07-30  5:53 dpdklab
2023-07-30  5:52 dpdklab
2023-07-30  5:47 dpdklab
2023-07-30  5:46 dpdklab
2023-07-30  5:45 dpdklab
2023-07-30  5:25 dpdklab
2023-07-30  5:12 dpdklab
2023-07-30  5:10 dpdklab
2023-07-30  5:06 dpdklab
2023-07-30  5:06 dpdklab
2023-07-30  5:05 dpdklab
2023-07-30  5:04 dpdklab
2023-07-30  5:00 dpdklab
2023-07-29 12:21 dpdklab
2023-07-29  7:39 dpdklab
2023-07-29  7:09 dpdklab
2023-07-29  7:08 dpdklab
2023-07-29  7:00 dpdklab
2023-07-29  6:55 dpdklab
2023-07-29  6:35 dpdklab
2023-07-29  6:29 dpdklab
2023-07-29  6:25 dpdklab
2023-07-29  6:24 dpdklab
2023-07-29  6:22 dpdklab
2023-07-29  6:19 dpdklab
2023-07-29  6:16 dpdklab
2023-07-29  6:11 dpdklab
2023-07-29  6:04 dpdklab
2023-07-29  5:48 dpdklab
2023-07-29  5:41 dpdklab
2023-07-29  5:26 dpdklab
2023-07-29  5:14 dpdklab
2023-07-29  5:10 dpdklab
2023-07-29  5:09 dpdklab
2023-07-29  5:08 dpdklab
2023-07-29  5:05 dpdklab
2023-07-29  5:02 dpdklab
2023-07-29  5:01 dpdklab
2023-07-28 14:15 dpdklab
2023-07-28 14:08 dpdklab
2023-07-28  7:20 dpdklab
2023-07-28  7:00 dpdklab
2023-07-28  6:51 dpdklab
2023-07-28  6:25 dpdklab
2023-07-28  6:25 dpdklab
2023-07-28  6:23 dpdklab
2023-07-28  6:18 dpdklab
2023-07-28  6:15 dpdklab
2023-07-28  6:13 dpdklab
2023-07-28  6:13 dpdklab
2023-07-28  6:11 dpdklab
2023-07-28  6:08 dpdklab
2023-07-28  6:07 dpdklab
2023-07-28  6:05 dpdklab
2023-07-28  5:50 dpdklab
2023-07-28  5:48 dpdklab
2023-07-28  5:37 dpdklab
2023-07-28  5:10 dpdklab
2023-07-28  5:05 dpdklab
2023-07-28  5:04 dpdklab
2023-07-28  5:02 dpdklab
2023-07-28  5:02 dpdklab
2023-07-28  5:02 dpdklab
2023-07-28  4:59 dpdklab
2023-07-27 19:07 dpdklab
2023-07-27 18:56 dpdklab
2023-07-27 18:12 dpdklab
2023-07-27 17:15 dpdklab
2023-07-27 17:08 dpdklab
2023-07-27 17:03 dpdklab
2023-07-27 16:45 dpdklab
2023-07-27 16:39 dpdklab
2023-07-27 16:06 dpdklab
2023-07-27 15:25 dpdklab
2023-07-27  8:02 dpdklab
2023-07-27  7:18 dpdklab
2023-07-27  7:00 dpdklab
2023-07-27  6:49 dpdklab
2023-07-27  6:36 dpdklab
2023-07-27  6:35 dpdklab
2023-07-27  6:34 dpdklab
2023-07-27  6:32 dpdklab
2023-07-27  6:29 dpdklab
2023-07-27  6:18 dpdklab
2023-07-27  6:14 dpdklab
2023-07-27  5:28 dpdklab
2023-07-27  5:23 dpdklab
2023-07-27  5:08 dpdklab
2023-07-27  5:05 dpdklab
2023-07-27  5:05 dpdklab
2023-07-27  5:03 dpdklab
2023-07-27  5:02 dpdklab
2023-07-27  4:59 dpdklab
2023-07-27  4:58 dpdklab
2023-07-27  4:57 dpdklab
2023-07-27  4:46 dpdklab
2023-07-27  4:45 dpdklab
2023-07-27  4:28 dpdklab
2023-07-27  4:07 dpdklab
2023-07-27  3:31 dpdklab
2023-07-27  3:30 dpdklab
2023-07-27  3:27 dpdklab
2023-07-27  3:27 dpdklab
2023-07-27  3:24 dpdklab
2023-07-27  3:24 dpdklab
2023-07-27  3:23 dpdklab
2023-07-27  3:22 dpdklab
2023-07-27  3:19 dpdklab
2023-07-27  3:10 dpdklab
2023-07-27  3:05 dpdklab
2023-07-27  3:03 dpdklab
2023-07-27  3:02 dpdklab
2023-07-27  3:00 dpdklab
2023-07-27  3:00 dpdklab
2023-07-27  3:00 dpdklab
2023-07-27  3:00 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=64c1dfb5.050a0220.a6114.0e38SMTPIN_ADDED_MISSING@mx.google.com \
    --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).