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| pw138655 [PATCH] [v3] app/test: fix rsa tests in qat suite
Date: Sat, 23 Mar 2024 01:35:01 -0700 (PDT)	[thread overview]
Message-ID: <65fe9435.050a0220.84dfb.f559SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240321083502.30552-1-arkadiuszx.kusztal@intel.com>

Test-Label: iol-broadcom-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/138655

_Performance Testing PASS_

Submitter: Arkadiusz Kusztal <arkadiuszx.kusztal@intel.com>
Date: Thursday, March 21 2024 08:35:02 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:7f82e9c89f3514715533feb34f46ff1ea95c6f98

138655 --> performance testing pass

Test environment and result as below:

Ubuntu 22.04 ARM
Kernel: 5.15.83+
Compiler: gcc 11.4.0
NIC: Arm Broadcom Inc. brcm_57414 25000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/2

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

Ubuntu 22.04
Kernel: 5.15.0-100-generic
Compiler: gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
NIC: Broadcom Inc. and subsidiaries BCM57414 NetXtreme-E 10Gb/25Gb RDMA Ethernet Controller 16d7 25 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/3

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

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-03-23  8:35 UTC|newest]

Thread overview: 81+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240321083502.30552-1-arkadiuszx.kusztal@intel.com>
2024-03-21  8:23 ` |SUCCESS| pw138655 [PATCH v3] " qemudev
2024-03-21  8:28 ` qemudev
2024-03-21  8:36 ` checkpatch
2024-03-21  9:24 ` 0-day Robot
2024-03-21 10:37 ` |SUCCESS| pw138655 [PATCH] [v3] " dpdklab
2024-03-21 10:43 ` dpdklab
2024-03-21 10:56 ` dpdklab
2024-03-21 10:56 ` dpdklab
2024-03-21 11:10 ` dpdklab
2024-03-21 11:11 ` dpdklab
2024-03-21 11:13 ` dpdklab
2024-03-21 11:15 ` dpdklab
2024-03-21 11:17 ` dpdklab
2024-03-21 11:18 ` dpdklab
2024-03-21 11:20 ` dpdklab
2024-03-21 11:35 ` dpdklab
2024-03-21 11:38 ` dpdklab
2024-03-21 11:38 ` dpdklab
2024-03-21 11:39 ` dpdklab
2024-03-21 11:39 ` dpdklab
2024-03-21 11:39 ` dpdklab
2024-03-21 11:39 ` dpdklab
2024-03-21 11:42 ` dpdklab
2024-03-21 11:42 ` dpdklab
2024-03-21 11:42 ` dpdklab
2024-03-21 11:43 ` dpdklab
2024-03-21 12:25 ` dpdklab
2024-03-21 12:33 ` dpdklab
2024-03-21 12:33 ` dpdklab
2024-03-21 12:40 ` dpdklab
2024-03-21 12:43 ` dpdklab
2024-03-21 12:43 ` dpdklab
2024-03-21 12:43 ` dpdklab
2024-03-21 12:45 ` dpdklab
2024-03-21 12:46 ` dpdklab
2024-03-21 12:46 ` dpdklab
2024-03-21 12:46 ` dpdklab
2024-03-21 12:46 ` dpdklab
2024-03-21 12:47 ` dpdklab
2024-03-21 12:47 ` dpdklab
2024-03-21 12:47 ` dpdklab
2024-03-21 12:48 ` dpdklab
2024-03-21 12:48 ` dpdklab
2024-03-21 12:48 ` dpdklab
2024-03-21 12:49 ` dpdklab
2024-03-21 12:49 ` dpdklab
2024-03-21 12:49 ` dpdklab
2024-03-21 12:49 ` dpdklab
2024-03-21 12:49 ` dpdklab
2024-03-21 12:49 ` dpdklab
2024-03-21 12:49 ` dpdklab
2024-03-21 12:50 ` dpdklab
2024-03-21 12:50 ` dpdklab
2024-03-21 12:50 ` dpdklab
2024-03-21 12:50 ` dpdklab
2024-03-21 12:50 ` dpdklab
2024-03-21 12:51 ` dpdklab
2024-03-21 12:51 ` dpdklab
2024-03-21 12:52 ` dpdklab
2024-03-21 12:52 ` dpdklab
2024-03-21 12:53 ` dpdklab
2024-03-21 12:53 ` dpdklab
2024-03-21 12:54 ` dpdklab
2024-03-21 12:55 ` dpdklab
2024-03-21 12:55 ` dpdklab
2024-03-21 12:56 ` dpdklab
2024-03-21 12:56 ` dpdklab
2024-03-21 12:57 ` dpdklab
2024-03-21 12:57 ` dpdklab
2024-03-21 12:58 ` dpdklab
2024-03-21 12:58 ` dpdklab
2024-03-21 12:58 ` dpdklab
2024-03-21 12:58 ` dpdklab
2024-03-21 12:58 ` dpdklab
2024-03-21 13:06 ` dpdklab
2024-03-21 15:04 ` dpdklab
2024-03-21 16:04 ` dpdklab
2024-03-21 16:17 ` dpdklab
2024-03-22  1:44 ` dpdklab
2024-03-23  8:35 ` dpdklab [this message]
2024-03-23  9:11 ` 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=65fe9435.050a0220.84dfb.f559SMTPIN_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).