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] c66daa12e76d7b4912cfb7109a761856a7a873ab
Date: Thu, 26 Dec 2024 23:33:03 -0800 (PST)	[thread overview]
Message-ID: <676e582f.050a0220.27223a.5e0dSMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Performance Testing PASS_

Branch: tags/v23.11

c66daa12e76d7b4912cfb7109a761856a7a873ab --> performance testing pass

Upstream job id: Template-DTS-Pipeline#204538

Test environment and result as below:

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.5%                        |
+------------+---------+----------+-------------+------------------------------+
| 64         | 2048    | 1        | 1           | 0.1%                         |
+------------+---------+----------+-------------+------------------------------+

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           | -0.6%                        |
+------------+---------+----------+-------------+------------------------------+
| 64         | 512     | 1        | 1           | -0.5%                        |
+------------+---------+----------+-------------+------------------------------+
| 64         | 2048    | 1        | 1           | 0.1%                         |
+------------+---------+----------+-------------+------------------------------+

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-12-27  7:33 UTC|newest]

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