automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Patrick Robb <probb@iol.unh.edu>, Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu, Radu Nicolau <radu.nicolau@intel.com>
Subject: |FAILURE| pw137198 [PATCH] [v3] examples/ipsec-secgw: fix cryptodev
Date: Tue, 27 Feb 2024 17:03:19 -0800 (PST)	[thread overview]
Message-ID: <65de8657.170a0220.c6346.0decSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240226102545.18667-1-radu.nicolau@intel.com>

Test-Label: iol-broadcom-Performance
Test-Status: FAILURE
http://dpdk.org/patch/137198

_Performance Testing issues_

Submitter: Radu Nicolau <radu.nicolau@intel.com>
Date: Monday, February 26 2024 10:25:45 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:92c0ad70caf3ed6f4b93de6ddaf7bc369737c049

137198 --> performance testing fail

Test environment and result as below:

Ubuntu 22.04
Kernel: 5.15.0-39-generic
Compiler: gcc gcc (Ubuntu 11.2.0-19ubuntu1) 11.2.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: 1/3

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

Ubuntu 22.04 ARM
Kernel: 5.15.82
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           | -2.0%                        |
+------------+---------+----------+-------------+------------------------------+

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-02-28  1:03 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240226102545.18667-1-radu.nicolau@intel.com>
2024-02-26 10:03 ` |SUCCESS| pw137198 [PATCH v3] examples/ipsec-secgw: fix cryptodev to SA mapping qemudev
2024-02-26 10:08 ` qemudev
2024-02-26 10:27 ` |WARNING| " checkpatch
2024-02-26 11:24 ` |SUCCESS| " 0-day Robot
2024-02-27 23:22 ` |SUCCESS| pw137198 [PATCH] [v3] examples/ipsec-secgw: fix cryptodev dpdklab
2024-02-27 23:31 ` dpdklab
2024-02-28  1:03 ` dpdklab [this message]
2024-02-28  1:11 ` dpdklab
2024-02-28  1:21 ` dpdklab
2024-02-28  1:28 ` dpdklab
2024-02-28  4:38 ` |FAILURE| " dpdklab
2024-02-28  4:43 ` |SUCCESS| " dpdklab
2024-02-28  4:48 ` dpdklab
2024-02-29 18:19 ` dpdklab
2024-03-06  4:19 ` |FAILURE| " dpdklab
2024-03-06  5:02 ` dpdklab
2024-02-27  7:47 dpdklab
  -- strict thread matches above, loose matches on Subject: below --
2024-02-26 16:29 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=65de8657.170a0220.c6346.0decSMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=probb@iol.unh.edu \
    --cc=radu.nicolau@intel.com \
    --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).