automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Ali Alnubani <alialnu@nvidia.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] d75221031514c432abcc02f46fbc349befd50617
Date: Thu, 12 Dec 2024 23:40:45 -0800 (PST)	[thread overview]
Message-ID: <675be4fd.170a0220.3d6d1a.a6d9SMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Performance Testing PASS_

Branch: tags/v22.11

d75221031514c432abcc02f46fbc349befd50617 --> performance testing pass

Upstream job id: Template-DTS-Pipeline#201988

Test environment and result as below:

Ubuntu 24.04
Kernel: 6.8.0-45-generic
Compiler: gcc 13.2.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.2%                        |
+------------+---------+----------+-------------+------------------------------+
| 128        | 1024    | 1        | 1           | 0.3%                         |
+------------+---------+----------+-------------+------------------------------+
| 256        | 1024    | 1        | 1           | 0.0%                         |
+------------+---------+----------+-------------+------------------------------+
| 512        | 1024    | 1        | 1           | -0.1%                        |
+------------+---------+----------+-------------+------------------------------+
| 1024       | 1024    | 1        | 1           | 0.2%                         |
+------------+---------+----------+-------------+------------------------------+
| 1518       | 1024    | 1        | 1           | -0.1%                        |
+------------+---------+----------+-------------+------------------------------+

Ubuntu 24.04
Kernel: 6.8.0-45-generic
Compiler: gcc 13.2.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.2%                        |
+------------+---------+----------+-------------+------------------------------+
| 128        | 1024    | 1        | 1           | -0.0%                        |
+------------+---------+----------+-------------+------------------------------+
| 256        | 1024    | 1        | 1           | -0.1%                        |
+------------+---------+----------+-------------+------------------------------+
| 512        | 1024    | 1        | 1           | -0.1%                        |
+------------+---------+----------+-------------+------------------------------+
| 1024       | 1024    | 1        | 1           | 0.2%                         |
+------------+---------+----------+-------------+------------------------------+
| 1518       | 1024    | 1        | 1           | -0.1%                        |
+------------+---------+----------+-------------+------------------------------+

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-12-13  7:40 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-13  7:40 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-12-13 11:51 dpdklab
2024-12-13 11:44 dpdklab
2024-12-13 10:49 dpdklab
2024-12-13  9:03 dpdklab
2024-12-13  9:02 dpdklab
2024-12-13  8:48 dpdklab
2024-12-13  8:03 dpdklab
2024-12-13  7:58 dpdklab
2024-12-13  7:48 dpdklab
2024-12-13  7:44 dpdklab
2024-12-13  7:32 dpdklab
2024-12-13  7:26 dpdklab
2024-12-11  9:02 dpdklab
2024-12-11  8:17 dpdklab
2024-12-11  7:38 dpdklab
2024-12-11  7:03 dpdklab
2024-12-11  6:33 dpdklab
2024-12-11  5:53 dpdklab
2024-12-11  5:42 dpdklab
2024-12-11  5:40 dpdklab
2024-12-11  5:37 dpdklab
2024-12-11  5:36 dpdklab
2024-12-11  5:33 dpdklab
2024-12-11  5:33 dpdklab
2024-12-11  5:22 dpdklab
2024-12-11  5:17 dpdklab
2024-12-10  8:08 dpdklab
2024-12-10  7:58 dpdklab
2024-12-10  7:34 dpdklab
2024-12-10  7:30 dpdklab
2024-12-10  7:30 dpdklab
2024-12-10  7:07 dpdklab
2024-12-10  6:56 dpdklab
2024-12-10  6:54 dpdklab
2024-12-10  6:49 dpdklab
2024-12-10  6:37 dpdklab
2024-12-10  6:37 dpdklab
2024-12-10  6:30 dpdklab
2024-12-10  6:26 dpdklab
2024-12-10  5:54 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=675be4fd.170a0220.3d6d1a.a6d9SMTPIN_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).