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
Subject: |SUCCESS| pw141917 [PATCH] app/eventdev: increase default queue dept
Date: Thu, 27 Jun 2024 08:47:59 -0700 (PDT)	[thread overview]
Message-ID: <667d89af.170a0220.2817c.3d09SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240627051524.1682347-1-asasidharan@marvell.com>

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

_Performance Testing PASS_

Submitter: Aakash Sasidharan <asasidharan@marvell.com>
Date: Thursday, June 27 2024 05:15:24 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:9985c7bc4b1f3ddb027951d419a5154c65b2a416

141917 --> performance testing pass

Test environment and result as below:

Ubuntu 22.04
Kernel: 5.15.0-94-generic
Compiler: gcc 11.4.0
NIC: Mellanox ConnectX-6 Lx 25000 Mbps
Target: Unknown
Fail/Total: 0/6

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

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-06-27 15:48 UTC|newest]

Thread overview: 113+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240627051524.1682347-1-asasidharan@marvell.com>
2024-06-27  4:55 ` |SUCCESS| pw141917 [PATCH] app/eventdev: increase default queue depth for cryptodev qemudev
2024-06-27  5:00 ` qemudev
2024-06-27  5:16 ` checkpatch
2024-06-27  6:05 ` 0-day Robot
2024-06-27 15:47 ` dpdklab [this message]
2024-06-27 17:03 ` |SUCCESS| pw141917 [PATCH] app/eventdev: increase default queue dept dpdklab
2024-06-27 17:17 ` dpdklab
2024-06-27 17:50 ` dpdklab
2024-06-27 18:03 ` dpdklab
2024-06-27 18:47 ` |PENDING| " dpdklab
2024-06-27 18:53 ` dpdklab
2024-06-27 19:10 ` dpdklab
2024-06-27 19:11 ` dpdklab
2024-06-27 19:18 ` dpdklab
2024-06-27 19:19 ` dpdklab
2024-06-27 19:19 ` dpdklab
2024-06-27 19:21 ` dpdklab
2024-06-27 19:22 ` dpdklab
2024-06-27 19:24 ` dpdklab
2024-06-27 19:33 ` dpdklab
2024-06-27 19:35 ` dpdklab
2024-06-27 19:40 ` dpdklab
2024-06-27 19:45 ` dpdklab
2024-06-27 19:47 ` dpdklab
2024-06-27 19:58 ` |SUCCESS| " dpdklab
2024-06-27 20:00 ` dpdklab
2024-06-27 20:16 ` dpdklab
2024-06-27 20:23 ` dpdklab
2024-06-27 20:37 ` dpdklab
2024-06-27 21:37 ` dpdklab
2024-06-27 21:39 ` dpdklab
2024-06-27 21:42 ` dpdklab
2024-06-27 21:44 ` dpdklab
2024-06-27 22:21 ` dpdklab
2024-06-27 22:22 ` dpdklab
2024-06-27 23:06 ` dpdklab
2024-06-27 23:15 ` dpdklab
2024-06-27 23:49 ` dpdklab
2024-06-28  1:07 ` dpdklab
2024-06-28  1:12 ` dpdklab
2024-06-28  1:17 ` dpdklab
2024-06-28  1:47 ` dpdklab
2024-06-28  2:23 ` dpdklab
2024-06-28  2:28 ` dpdklab
2024-06-28  2:30 ` dpdklab
2024-06-28  2:31 ` dpdklab
2024-06-28  2:33 ` dpdklab
2024-06-28  2:38 ` dpdklab
2024-06-28  2:39 ` dpdklab
2024-06-28  2:41 ` dpdklab
2024-06-28  2:41 ` dpdklab
2024-06-28  2:43 ` dpdklab
2024-06-28  2:43 ` dpdklab
2024-06-28  2:44 ` dpdklab
2024-06-28  2:44 ` dpdklab
2024-06-28  2:44 ` dpdklab
2024-06-28  2:44 ` dpdklab
2024-06-28  2:45 ` dpdklab
2024-06-28  2:46 ` dpdklab
2024-06-28  2:46 ` dpdklab
2024-06-28  2:48 ` dpdklab
2024-06-28  2:49 ` dpdklab
2024-06-28  2:51 ` dpdklab
2024-06-28  2:52 ` dpdklab
2024-06-28  2:52 ` dpdklab
2024-06-28  2:53 ` dpdklab
2024-06-28  2:53 ` dpdklab
2024-06-28  2:55 ` dpdklab
2024-06-28  2:57 ` dpdklab
2024-06-28  2:57 ` dpdklab
2024-06-28  2:58 ` dpdklab
2024-06-28  3:00 ` dpdklab
2024-06-28  3:01 ` dpdklab
2024-06-28  3:03 ` dpdklab
2024-06-28  3:05 ` dpdklab
2024-06-28  3:08 ` dpdklab
2024-06-28  3:25 ` dpdklab
2024-06-28  3:25 ` dpdklab
2024-06-28  3:26 ` dpdklab
2024-06-28  3:27 ` dpdklab
2024-06-28  3:31 ` dpdklab
2024-06-28  3:33 ` dpdklab
2024-06-28  3:34 ` dpdklab
2024-06-28  3:35 ` dpdklab
2024-06-28  3:38 ` dpdklab
2024-06-28  3:40 ` dpdklab
2024-06-28  3:41 ` dpdklab
2024-06-28  3:45 ` dpdklab
2024-06-28  3:49 ` dpdklab
2024-06-28  3:51 ` dpdklab
2024-06-28  3:53 ` dpdklab
2024-06-28  4:45 ` dpdklab
2024-06-28  4:57 ` dpdklab
2024-06-28  5:00 ` dpdklab
2024-06-28  5:02 ` dpdklab
2024-06-28  5:07 ` dpdklab
2024-06-28  5:08 ` dpdklab
2024-06-28  5:09 ` dpdklab
2024-06-28  5:15 ` dpdklab
2024-06-28  5:16 ` dpdklab
2024-06-28  5:23 ` dpdklab
2024-06-28  5:37 ` dpdklab
2024-06-28  5:43 ` dpdklab
2024-06-28  5:45 ` dpdklab
2024-06-28  5:48 ` dpdklab
2024-06-28  5:50 ` dpdklab
2024-06-28  5:52 ` dpdklab
2024-06-28  5:53 ` dpdklab
2024-06-28  5:55 ` dpdklab
2024-06-28  5:55 ` dpdklab
2024-06-28 14:46 ` dpdklab
2024-06-28 15:02 ` dpdklab
2024-06-29  3: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=667d89af.170a0220.2817c.3d09SMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --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).