automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>, Patrick Robb <probb@iol.unh.edu>
Cc: dpdk-test-reports@iol.unh.edu, Xueming Li <xuemingl@nvidia.com>,
	Christian Ehrhardt <christian.ehrhardt@canonical.com>,
	Kevin Traynor <ktraynor@redhat.com>,
	Luca Boccassi <bluca@debian.org>
Subject: |FAILURE| [GIT MASTER] 9dae7a15aea76313c592c11db44e1386e85f86fe
Date: Fri, 10 Feb 2023 05:34:07 +0000 (UTC)	[thread overview]
Message-ID: <20230210053407.BBBA0601CD@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)

[-- Attachment #1: Type: text/plain, Size: 2312 bytes --]

_Performance Testing issues_

Branch: tags/v22.11

9dae7a15aea76313c592c11db44e1386e85f86fe --> performance testing fail

Test environment and result as below:

Ubuntu 20.04 ARM
Kernel: 4.15.0-132-generic
Compiler: gcc 7.5
NIC: Arm Broadcom Inc. brcm_57414 25000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 1/2

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

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: 0/3

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

To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/23263/

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-02-10  5:34 UTC|newest]

Thread overview: 91+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-10  5:34 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-04-16  5:38 dpdklab
2023-04-16  5:36 dpdklab
2023-04-15 10:29 dpdklab
2023-04-15  7:10 dpdklab
2023-04-14  6:02 dpdklab
2023-04-14  5:31 dpdklab
2023-04-13  5:35 dpdklab
2023-04-13  5:23 dpdklab
2023-04-12  5:35 dpdklab
2023-04-11  5:16 dpdklab
2023-04-10  4:48 dpdklab
2023-04-09  5:02 dpdklab
2023-04-08  5:09 dpdklab
2023-04-07  5:12 dpdklab
2023-04-06 12:10 dpdklab
2023-04-05  4:32 dpdklab
2023-04-05  4:23 dpdklab
2023-04-05  4:15 dpdklab
2023-04-04  4:46 dpdklab
2023-04-03  4:42 dpdklab
2023-04-02  4:50 dpdklab
2023-04-01  4:54 dpdklab
2023-03-31 18:52 dpdklab
2023-03-31 18:41 dpdklab
2023-03-29  4:45 dpdklab
2023-03-29  4:40 dpdklab
2023-03-29  4:31 dpdklab
2023-03-29  4:28 dpdklab
2023-03-16  5:02 dpdklab
2023-02-23  5:43 dpdklab
2023-02-23  5:34 dpdklab
2023-02-22  5:33 dpdklab
2023-02-19  5:44 dpdklab
2023-02-19  5:31 dpdklab
2023-02-19  5:28 dpdklab
2023-02-11  5:31 dpdklab
2023-02-11  5:31 dpdklab
2023-02-11  5:27 dpdklab
2023-02-10  5:18 dpdklab
2023-01-22  5:23 dpdklab
2023-01-19  5:24 dpdklab
2023-01-13  5:43 dpdklab
2023-01-13  5:39 dpdklab
2023-01-13  5:24 dpdklab
2023-01-11 15:08 dpdklab
2023-01-11  5:41 dpdklab
2023-01-10  5:30 dpdklab
2023-01-10  5:27 dpdklab
2023-01-07  5:43 dpdklab
2023-01-07  5:27 dpdklab
2023-01-05  5:24 dpdklab
2023-01-02  5:23 dpdklab
2022-12-29  6:46 dpdklab
2022-12-29  6:46 dpdklab
2022-12-29  6:46 dpdklab
2022-12-29  6:45 dpdklab
2022-12-29  6:45 dpdklab
2022-12-29  6:45 dpdklab
2022-12-29  5:22 dpdklab
2022-12-28  5:42 dpdklab
2022-12-28  5:38 dpdklab
2022-12-26  7:02 dpdklab
2022-12-26  7:02 dpdklab
2022-12-26  7:02 dpdklab
2022-12-26  7:01 dpdklab
2022-12-21  9:56 dpdklab
2022-12-21  9:55 dpdklab
2022-12-21  9:55 dpdklab
2022-12-21  9:52 dpdklab
2022-12-21  9:52 dpdklab
2022-12-21  9:52 dpdklab
2022-12-21  9:52 dpdklab
2022-12-20  7:11 dpdklab
2022-12-20  7:10 dpdklab
2022-12-20  7:07 dpdklab
2022-12-20  7:07 dpdklab
2022-12-20  7:07 dpdklab
2022-12-20  7:07 dpdklab
2022-12-20  6:40 dpdklab
2022-12-04  6:44 dpdklab
2022-12-04  6:43 dpdklab
2022-12-04  6:40 dpdklab
2022-12-04  6:34 dpdklab
2022-12-04  6:34 dpdklab
2022-12-04  6:33 dpdklab
2022-12-04  6:33 dpdklab
2022-12-04  6:32 dpdklab
2022-12-04  6:26 dpdklab
2022-12-04  5:30 dpdklab
2022-12-04  5:26 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=20230210053407.BBBA0601CD@dpdk-ubuntu.dpdklab.iol.unh.edu \
    --to=dpdklab@iol.unh.edu \
    --cc=bluca@debian.org \
    --cc=christian.ehrhardt@canonical.com \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=ktraynor@redhat.com \
    --cc=probb@iol.unh.edu \
    --cc=test-report@dpdk.org \
    --cc=xuemingl@nvidia.com \
    /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).