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| pw148826 [PATCH] test: raise fast test timeout to 60s on R
Date: Tue, 26 Nov 2024 02:55:07 -0800 (PST)	[thread overview]
Message-ID: <6745a90b.050a0220.19dc12.b629SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <MW4PR11MB8289B816B08C6E19716B8F82D72C2@MW4PR11MB8289.namprd11.prod.outlook.com>

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

_Performance Testing PASS_

Submitter: Eric Long <i@hack3r.moe>
Date: Saturday, November 23 2024 14:58:10 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:f4ccce58c1a33cb41e1e820da504698437987efc

148826 --> performance testing pass

Upstream job id: Template-DTS-Pipeline#198864

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/4

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

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.2%                         |
+----------+-------------+---------+------------+------------------------------+
| 1        | 2           | 2048    | 64         | -0.2%                        |
+----------+-------------+---------+------------+------------------------------+
| 1        | 1           | 128     | 64         | -0.2%                        |
+----------+-------------+---------+------------+------------------------------+
| 1        | 1           | 512     | 64         | -0.5%                        |
+----------+-------------+---------+------------+------------------------------+
| 1        | 1           | 2048    | 64         | 0.4%                         |
+----------+-------------+---------+------------+------------------------------+

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.2%                         |
+----------+-------------+---------+------------+------------------------------+
| 1        | 2           | 2048    | 64         | -1.3%                        |
+----------+-------------+---------+------------+------------------------------+
| 1        | 1           | 512     | 64         | -1.7%                        |
+----------+-------------+---------+------------+------------------------------+
| 1        | 1           | 2048    | 64         | -3.9%                        |
+----------+-------------+---------+------------+------------------------------+

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-11-26 10:55 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <MW4PR11MB8289B816B08C6E19716B8F82D72C2@MW4PR11MB8289.namprd11.prod.outlook.com>
2024-11-23 14:29 ` |SUCCESS| pw148826 [PATCH] test: raise fast test timeout to 60s on RISC-V qemudev
2024-11-23 14:33 ` qemudev
2024-11-23 15:01 ` checkpatch
2024-11-23 15:36 ` |PENDING| pw148826 [PATCH] test: raise fast test timeout to 60s on R dpdklab
2024-11-23 15:44 ` |SUCCESS| " dpdklab
2024-11-23 15:47 ` |PENDING| " dpdklab
2024-11-23 16:01 ` |SUCCESS| " dpdklab
2024-11-23 16:03 ` dpdklab
2024-11-23 16:03 ` |SUCCESS| pw148826 [PATCH] test: raise fast test timeout to 60s on RISC-V 0-day Robot
2024-11-23 16:08 ` |SUCCESS| pw148826 [PATCH] test: raise fast test timeout to 60s on R dpdklab
2024-11-23 16:12 ` dpdklab
2024-11-23 16:13 ` dpdklab
2024-11-23 16:15 ` dpdklab
2024-11-23 16:15 ` dpdklab
2024-11-23 16:19 ` dpdklab
2024-11-23 16:32 ` dpdklab
2024-11-23 16:37 ` dpdklab
2024-11-23 17:58 ` dpdklab
2024-11-26 10:55 ` dpdklab [this message]
2024-11-26 11:06 ` 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=6745a90b.050a0220.19dc12.b629SMTPIN_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).