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| pw149013-149014 [PATCH] [v3,2/2] usertools/devbind: replac
Date: Wed, 04 Dec 2024 02:41:08 -0800 (PST)	[thread overview]
Message-ID: <675031c4.630a0220.be336.56f8SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <b8aa13c9ed8989e73e9352ea905f6956a863148d.1733305655.git.anatoly.burakov@intel.com>

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

_Performance Testing PASS_

Submitter: Burakov, Anatoly <anatoly.burakov@intel.com>
Date: Wednesday, December 04 2024 09:47:38 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:1b3bf1128d9bda5595861814792f74b8f57160c8

149013-149014 --> performance testing pass

Upstream job id: Template-DTS-Pipeline#200979

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           | 1.2%                         |
+------------+---------+----------+-------------+------------------------------+
| 128        | 1024    | 1        | 1           | 1.6%                         |
+------------+---------+----------+-------------+------------------------------+
| 256        | 1024    | 1        | 1           | -1.1%                        |
+------------+---------+----------+-------------+------------------------------+
| 512        | 1024    | 1        | 1           | 0.1%                         |
+------------+---------+----------+-------------+------------------------------+
| 1024       | 1024    | 1        | 1           | -0.2%                        |
+------------+---------+----------+-------------+------------------------------+
| 1518       | 1024    | 1        | 1           | 0.2%                         |
+------------+---------+----------+-------------+------------------------------+

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

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

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-04 10:41 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <b8aa13c9ed8989e73e9352ea905f6956a863148d.1733305655.git.anatoly.burakov@intel.com>
2024-12-04  9:15 ` |SUCCESS| pw149013-149014 [PATCH v3 2/2] usertools/devbind: replace devbind qemudev
2024-12-04  9:20 ` qemudev
2024-12-04  9:49 ` |WARNING| pw149014 " checkpatch
2024-12-04 10:23 ` |PENDING| pw149013-149014 [PATCH] [v3,2/2] usertools/devbind: replac dpdklab
2024-12-04 10:34 ` |SUCCESS| " dpdklab
2024-12-04 10:41 ` dpdklab [this message]
2024-12-04 10:42 ` |SUCCESS| pw149014 [PATCH v3 2/2] usertools/devbind: replace devbind 0-day Robot
2024-12-04 10:42 ` |PENDING| pw149013-149014 [PATCH] [v3,2/2] usertools/devbind: replac dpdklab
2024-12-04 10:43 ` |SUCCESS| " dpdklab
2024-12-04 10:47 ` dpdklab
2024-12-04 10:55 ` dpdklab
2024-12-04 11:06 ` |WARNING| " dpdklab
2024-12-04 11:07 ` dpdklab
2024-12-04 11:17 ` |SUCCESS| " dpdklab
2024-12-04 11:20 ` dpdklab
2024-12-04 11:20 ` dpdklab
2024-12-04 11:46 ` dpdklab
2024-12-04 13:44 ` dpdklab
2024-12-04 15:14 ` dpdklab
2024-12-04 15:15 ` dpdklab
2024-12-04 15:21 ` dpdklab
2024-12-04 15:45 ` dpdklab
2024-12-04 15:47 ` dpdklab
2024-12-04 16:14 ` 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=675031c4.630a0220.be336.56f8SMTPIN_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).