automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>, Ali Alnubani <alialnu@nvidia.com>
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] b287e404643aeab5bb5db084c142789df187844e
Date: Wed, 01 Oct 2025 07:06:23 -0700 (PDT)	[thread overview]
Message-ID: <68dd355f.050a0220.2284fe.a721SMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Performance Testing PASS_

Branch: tags/v24.11

b287e404643aeab5bb5db084c142789df187844e --> performance testing pass

Upstream job id: Template-DTS-Pipeline#247278

Test environment and result as below:

Ubuntu 24.04
Kernel: 6.8
Compiler: gcc gcc (Ubuntu 13.3.0-6ubuntu2~24.04) 13.3.0
NIC: Mellanox ConnectX-6 Lx 25000 Mbps
Fail/Total: 0/6

Detail performance results: 
+------------+---------+----------+-------------+------------------------------+
| frame_size | txd/rxd | num_cpus | num_threads |  throughput difference from  |
|            |         |          |             |           expected           |
+============+=========+==========+=============+==============================+
| 64         | 1024    | 1        | 1           | 0.0%                         |
+------------+---------+----------+-------------+------------------------------+
| 128        | 1024    | 1        | 1           | 0.2%                         |
+------------+---------+----------+-------------+------------------------------+
| 256        | 1024    | 1        | 1           | 0.2%                         |
+------------+---------+----------+-------------+------------------------------+
| 512        | 1024    | 1        | 1           | 0.3%                         |
+------------+---------+----------+-------------+------------------------------+
| 1024       | 1024    | 1        | 1           | 0.2%                         |
+------------+---------+----------+-------------+------------------------------+
| 1518       | 1024    | 1        | 1           | 0.2%                         |
+------------+---------+----------+-------------+------------------------------+

Ubuntu 24.04
Kernel: 6.8
Compiler: gcc gcc (Ubuntu 13.3.0-6ubuntu2~24.04) 13.3.0
NIC: NVIDIA Mellanox ConnectX-7 100000 Mbps
Fail/Total: 0/6

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

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2025-10-01 14:06 UTC|newest]

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