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| pw143973-143974 [PATCH] [v10,2/2] examples/l3fwd-power: ad
Date: Thu, 12 Sep 2024 10:04:51 -0700 (PDT)	[thread overview]
Message-ID: <66e31f33.050a0220.301390.00faSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240912023812.30885-3-lihuisong@huawei.com>

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

_Performance Testing PASS_

Submitter: Huisong Li <lihuisong@huawei.com>
Date: Thursday, September 12 2024 02:38:12 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:41dd9a6bc2d9c6e20e139ad713cc9d172572dd43

143973-143974 --> performance testing pass

Upstream job id: Template-DTS-Pipeline#180201

Test environment and result as below:

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
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.6%                        |
+------------+---------+----------+-------------+------------------------------+
| 64         | 2048    | 1        | 1           | -0.5%                        |
+------------+---------+----------+-------------+------------------------------+

Ubuntu 22.04 ARM
Kernel: 5.15.83+
Compiler: gcc 11.4.0
NIC: Arm Broadcom Inc. brcm_57414 25000 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.1%                         |
+------------+---------+----------+-------------+------------------------------+
| 64         | 2048    | 1        | 1           | -0.2%                        |
+------------+---------+----------+-------------+------------------------------+

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-09-12 17:04 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240912023812.30885-3-lihuisong@huawei.com>
2024-09-12  2:21 ` |SUCCESS| pw143973-143974 [PATCH v10 2/2] examples/l3fwd-power: add PM QoS configuration qemudev
2024-09-12  2:25 ` qemudev
2024-09-12  2:48 ` |SUCCESS| pw143974 " checkpatch
2024-09-12  3:44 ` 0-day Robot
2024-09-12  9:20 ` |SUCCESS| pw143973-143974 [PATCH] [v10,2/2] examples/l3fwd-power: ad dpdklab
2024-09-12 10:00 ` dpdklab
2024-09-12 13:48 ` |PENDING| " dpdklab
2024-09-12 14:01 ` |SUCCESS| " dpdklab
2024-09-12 15:10 ` |PENDING| " dpdklab
2024-09-12 15:32 ` dpdklab
2024-09-12 15:55 ` dpdklab
2024-09-12 16:57 ` |SUCCESS| " dpdklab
2024-09-12 16:59 ` dpdklab
2024-09-12 17:01 ` dpdklab
2024-09-12 17:04 ` dpdklab [this message]
2024-09-12 17:09 ` dpdklab
2024-09-12 17:09 ` dpdklab
2024-09-12 17:14 ` dpdklab
2024-09-12 17:20 ` dpdklab
2024-09-12 17:58 ` dpdklab
2024-09-12 23:14 ` dpdklab
2024-09-15  7:38 ` dpdklab
2024-09-15 12:23 ` dpdklab
2024-09-18  7:55 ` 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=66e31f33.050a0220.301390.00faSMTPIN_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).