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] 3ca6090a4f1c8f831a5164296f54ce6912f994a9
Date: Mon, 11 Nov 2024 01:08:11 -0800 (PST)	[thread overview]
Message-ID: <6731c97b.250a0220.34bc19.fc1aSMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Performance Testing PASS_

Branch: tags/v22.11

3ca6090a4f1c8f831a5164296f54ce6912f994a9 --> performance testing pass

Upstream job id: Template-DTS-Pipeline#195270

Test environment and result as below:

Ubuntu 22.04
Kernel: 5.15.0-100-generic
Compiler: gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
NIC: Broadcom Inc. and subsidiaries BCM57414 NetXtreme-E 10Gb/25Gb RDMA Ethernet Controller 16d7 25 Mbps
Fail/Total: 0/3

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

Ubuntu 22.04 ARM
Kernel: 5.15.83+
Compiler: gcc 11.4.0
NIC: Arm Broadcom Inc. brcm_57414 25000 Mbps
Fail/Total: 0/2

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

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-11-11  9:08 UTC|newest]

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