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
Subject: |SUCCESS| pw149496-149498 [PATCH] [3/3] drivers/net: add diagnostics
Date: Thu, 26 Dec 2024 18:28:57 -0800 (PST)	[thread overview]
Message-ID: <676e10e9.050a0220.159bce.0063SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <1735263196-2809-4-git-send-email-andremue@linux.microsoft.com>

Test-Label: iol-mellanox-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/149498

_Performance Testing PASS_

Submitter: Andre Muezerie <andremue@linux.microsoft.com>
Date: Friday, December 27 2024 01:33:16 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:fd51012de5369679e807be1d6a81d63ef15015ce

149496-149498 --> performance testing pass

Upstream job id: Template-DTS-Pipeline#204487

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.9%                        |
+------------+---------+----------+-------------+------------------------------+
| 128        | 1024    | 1        | 1           | 0.5%                         |
+------------+---------+----------+-------------+------------------------------+
| 256        | 1024    | 1        | 1           | 0.6%                         |
+------------+---------+----------+-------------+------------------------------+
| 512        | 1024    | 1        | 1           | 0.0%                         |
+------------+---------+----------+-------------+------------------------------+
| 1024       | 1024    | 1        | 1           | -0.1%                        |
+------------+---------+----------+-------------+------------------------------+
| 1518       | 1024    | 1        | 1           | -0.0%                        |
+------------+---------+----------+-------------+------------------------------+

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.0%                         |
+------------+---------+----------+-------------+------------------------------+
| 128        | 1024    | 1        | 1           | 0.1%                         |
+------------+---------+----------+-------------+------------------------------+
| 256        | 1024    | 1        | 1           | -0.2%                        |
+------------+---------+----------+-------------+------------------------------+
| 512        | 1024    | 1        | 1           | -0.2%                        |
+------------+---------+----------+-------------+------------------------------+
| 1024       | 1024    | 1        | 1           | 0.1%                         |
+------------+---------+----------+-------------+------------------------------+
| 1518       | 1024    | 1        | 1           | 0.1%                         |
+------------+---------+----------+-------------+------------------------------+

To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/32218/

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-12-27  2:29 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1735263196-2809-4-git-send-email-andremue@linux.microsoft.com>
2024-12-27  1:07 ` |SUCCESS| pw149496-149498 [PATCH 3/3] drivers/net: add diagnostics macros to make code portable qemudev
2024-12-27  1:12 ` qemudev
2024-12-27  1:34 ` |SUCCESS| pw149498 " checkpatch
2024-12-27  2:14 ` |SUCCESS| pw149496-149498 [PATCH] [3/3] drivers/net: add diagnostics dpdklab
2024-12-27  2:23 ` |PENDING| " dpdklab
2024-12-27  2:25 ` |SUCCESS| pw149498 [PATCH 3/3] drivers/net: add diagnostics macros to make code portable 0-day Robot
2024-12-27  2:26 ` |PENDING| pw149496-149498 [PATCH] [3/3] drivers/net: add diagnostics dpdklab
2024-12-27  2:28 ` dpdklab [this message]
2024-12-27  2:30 ` |SUCCESS| " dpdklab
2024-12-27  2:32 ` |PENDING| " dpdklab
2024-12-27  2:33 ` |SUCCESS| " dpdklab
2024-12-27  2:36 ` dpdklab
2024-12-27  2:41 ` |PENDING| " dpdklab
2024-12-27  2:41 ` dpdklab
2024-12-27  2:41 ` |SUCCESS| " dpdklab
2024-12-27  2:46 ` |PENDING| " dpdklab
2024-12-27  3:20 ` |SUCCESS| " dpdklab
2024-12-27  3:22 ` dpdklab
2024-12-27  3:27 ` dpdklab
2024-12-27  3:36 ` |WARNING| " dpdklab
2024-12-27  4:32 ` |SUCCESS| " dpdklab
2024-12-27  5:43 ` 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=676e10e9.050a0220.159bce.0063SMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=alialnu@nvidia.com \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=test-report@dpdk.org \
    /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).