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| pw142787 [PATCH] doc: announce change in crypto queue setu
Date: Wed, 31 Jul 2024 08:17:39 -0700 (PDT)	[thread overview]
Message-ID: <66aa5593.050a0220.291339.12b6SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240731112037.1440890-1-gakhil@marvell.com>

Test-Label: iol-intel-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/142787

_Performance Testing PASS_

Submitter: Akhil Goyal <gakhil@marvell.com>
Date: Wednesday, July 31 2024 11:20:37 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:1d245ca8239d947258b3ae7cc4d8df97ef527852

142787 --> performance testing pass

Upstream job id: Template-DTS-Pipeline#172096

Test environment and result as below:

22.04
Kernel: 5.15.0-94-generic
Compiler: gcc 11.4.0
NIC: Intel E810 100000 Mbps
Fail/Total: 0/1

Detail performance results: 
The measurement deltas are not ready yet! Please check back later.

Ubuntu 20.04
Kernel: 5.4.0-122-generic
Compiler: gcc 9.4.0
NIC: Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Fail/Total: 0/4

Detail performance results: 
+----------+-------------+---------+------------+------------------------------+
| num_cpus | num_threads | txd/rxd | frame_size |  throughput difference from  |
|          |             |         |            |           expected           |
+==========+=============+=========+============+==============================+
| 1        | 2           | 512     | 64         | 0.8%                         |
+----------+-------------+---------+------------+------------------------------+
| 1        | 2           | 2048    | 64         | 2.3%                         |
+----------+-------------+---------+------------+------------------------------+
| 1        | 1           | 512     | 64         | 0.8%                         |
+----------+-------------+---------+------------+------------------------------+
| 1        | 1           | 2048    | 64         | 2.1%                         |
+----------+-------------+---------+------------+------------------------------+

Ubuntu 20.04 ARM
Kernel: 5.15.0-97-generic
Compiler: gcc 11.4.0
NIC: Arm Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Fail/Total: 0/2

Detail performance results: 
+------------+---------+----------+-------------+------------------------------+
| frame_size | txd/rxd | num_cpus | num_threads |  throughput difference from  |
|            |         |          |             |           expected           |
+============+=========+==========+=============+==============================+
| 64         | 512     | 1        | 1           | -0.0%                        |
+------------+---------+----------+-------------+------------------------------+
| 64         | 2048    | 1        | 1           | -0.1%                        |
+------------+---------+----------+-------------+------------------------------+

Ubuntu 20.04
Kernel: 5.4.0-122-generic
Compiler: gcc 9.4.0
NIC: Intel Corporation Ethernet Converged Network Adapter 82599ES 10000 Mbps
Fail/Total: 0/6

Detail performance results: 
+----------+-------------+---------+------------+------------------------------+
| num_cpus | num_threads | txd/rxd | frame_size |  throughput difference from  |
|          |             |         |            |           expected           |
+==========+=============+=========+============+==============================+
| 1        | 2           | 128     | 64         | 0.1%                         |
+----------+-------------+---------+------------+------------------------------+
| 1        | 2           | 512     | 64         | 0.1%                         |
+----------+-------------+---------+------------+------------------------------+
| 1        | 2           | 2048    | 64         | -0.1%                        |
+----------+-------------+---------+------------+------------------------------+
| 1        | 1           | 128     | 64         | -0.0%                        |
+----------+-------------+---------+------------+------------------------------+
| 1        | 1           | 512     | 64         | 0.2%                         |
+----------+-------------+---------+------------+------------------------------+
| 1        | 1           | 2048    | 64         | -0.1%                        |
+----------+-------------+---------+------------+------------------------------+

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-07-31 15:20 UTC|newest]

Thread overview: 99+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240731112037.1440890-1-gakhil@marvell.com>
2024-07-31 11:11 ` |SUCCESS| pw142787 [PATCH] doc: announce change in crypto queue setup qemudev
2024-07-31 11:15 ` qemudev
2024-07-31 11:26 ` checkpatch
2024-07-31 14:57 ` |SUCCESS| pw142787 [PATCH] doc: announce change in crypto queue setu dpdklab
2024-07-31 14:59 ` |PENDING| " dpdklab
2024-07-31 15:11 ` |SUCCESS| " dpdklab
2024-07-31 15:12 ` dpdklab
2024-07-31 15:17 ` dpdklab [this message]
2024-07-31 15:23 ` dpdklab
2024-07-31 15:25 ` dpdklab
2024-07-31 15:39 ` dpdklab
2024-07-31 16:26 ` dpdklab
2024-07-31 17:31 ` |PENDING| " dpdklab
2024-07-31 17:43 ` dpdklab
2024-07-31 17:45 ` dpdklab
2024-07-31 17:45 ` dpdklab
2024-07-31 17:45 ` dpdklab
2024-07-31 17:55 ` dpdklab
2024-07-31 17:57 ` dpdklab
2024-07-31 17:58 ` dpdklab
2024-07-31 18:03 ` dpdklab
2024-07-31 18:09 ` dpdklab
2024-07-31 18:10 ` dpdklab
2024-07-31 18:10 ` dpdklab
2024-07-31 18:12 ` dpdklab
2024-07-31 18:14 ` dpdklab
2024-07-31 18:20 ` |SUCCESS| " dpdklab
2024-07-31 19:08 ` dpdklab
2024-07-31 19:43 ` dpdklab
2024-07-31 20:02 ` |PENDING| " dpdklab
2024-07-31 20:08 ` dpdklab
2024-07-31 20:09 ` dpdklab
2024-07-31 20:10 ` dpdklab
2024-07-31 20:11 ` |SUCCESS| " dpdklab
2024-07-31 20:30 ` |PENDING| " dpdklab
2024-07-31 20:32 ` |SUCCESS| " dpdklab
2024-07-31 20:36 ` |PENDING| " dpdklab
2024-07-31 20:44 ` dpdklab
2024-07-31 20:45 ` dpdklab
2024-07-31 20:46 ` dpdklab
2024-07-31 20:52 ` dpdklab
2024-07-31 20:53 ` dpdklab
2024-07-31 20:55 ` dpdklab
2024-07-31 21:01 ` dpdklab
2024-07-31 21:08 ` dpdklab
2024-07-31 21:13 ` dpdklab
2024-07-31 21:14 ` dpdklab
2024-07-31 21:16 ` dpdklab
2024-07-31 21:16 ` dpdklab
2024-07-31 21:19 ` dpdklab
2024-07-31 21:19 ` dpdklab
2024-07-31 21:20 ` dpdklab
2024-07-31 21:21 ` dpdklab
2024-07-31 22:04 ` dpdklab
2024-07-31 22:17 ` |SUCCESS| " dpdklab
2024-07-31 23:13 ` |PENDING| " dpdklab
2024-07-31 23:16 ` dpdklab
2024-07-31 23:17 ` dpdklab
2024-07-31 23:18 ` dpdklab
2024-07-31 23:22 ` dpdklab
2024-07-31 23:24 ` dpdklab
2024-07-31 23:25 ` dpdklab
2024-07-31 23:29 ` dpdklab
2024-07-31 23:29 ` dpdklab
2024-07-31 23:33 ` dpdklab
2024-07-31 23:34 ` dpdklab
2024-07-31 23:37 ` dpdklab
2024-07-31 23:37 ` dpdklab
2024-07-31 23:38 ` dpdklab
2024-07-31 23:41 ` |SUCCESS| " dpdklab
2024-08-01  0:19 ` dpdklab
2024-08-01  0:19 ` |PENDING| " dpdklab
2024-08-01  0:39 ` dpdklab
2024-08-01  0:39 ` dpdklab
2024-08-01  0:39 ` dpdklab
2024-08-01  0:39 ` dpdklab
2024-08-01  0:40 ` dpdklab
2024-08-01  0:42 ` dpdklab
2024-08-01  0:43 ` dpdklab
2024-08-01  0:46 ` dpdklab
2024-08-01  0:49 ` dpdklab
2024-08-01  0:50 ` dpdklab
2024-08-01  0:52 ` dpdklab
2024-08-01  0:52 ` dpdklab
2024-08-01  0:52 ` dpdklab
2024-08-01  0:55 ` dpdklab
2024-08-01  0:57 ` dpdklab
2024-08-01  0:58 ` dpdklab
2024-08-01  0:58 ` dpdklab
2024-08-01  1:21 ` dpdklab
2024-08-01  1:25 ` dpdklab
2024-08-01  1:31 ` dpdklab
2024-08-01  1:33 ` dpdklab
2024-08-01  1:37 ` dpdklab
2024-08-01  1:50 ` dpdklab
2024-08-01  1:59 ` dpdklab
2024-08-01  2:12 ` dpdklab
2024-08-01  2:15 ` |SUCCESS| " dpdklab
2024-08-02  4:34 ` 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=66aa5593.050a0220.291339.12b6SMTPIN_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).