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| [GIT MASTER] a89a9ca38ae61778a80f287677dc91e8bb3fbdfd
Date: Thu, 28 Sep 2023 18:27:55 -0700 (PDT)	[thread overview]
Message-ID: <6516281b.170a0220.969c5.1e0bSMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Performance Testing PASS_

Branch: dpdk

a89a9ca38ae61778a80f287677dc91e8bb3fbdfd --> performance testing pass

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

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

Ubuntu 20.04 ARM
Kernel: 5.11.0-46-generic
Compiler: gcc 9.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.1%                        |
+------------+---------+----------+-------------+------------------------------+
| 64         | 2048    | 1        | 1           | 0.2%                         |
+------------+---------+----------+-------------+------------------------------+

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-09-29  1:28 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-29  1:27 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-09-29 10:19 dpdklab
2023-09-29  2:52 dpdklab
2023-09-29  2:43 dpdklab
2023-09-29  2:40 dpdklab
2023-09-29  2:40 dpdklab
2023-09-29  2:31 dpdklab
2023-09-29  2:28 dpdklab
2023-09-29  2:24 dpdklab
2023-09-29  2:23 dpdklab
2023-09-29  2:17 dpdklab
2023-09-29  2:15 dpdklab
2023-09-29  2:13 dpdklab
2023-09-29  2:09 dpdklab
2023-09-29  1:49 dpdklab
2023-09-29  1:45 dpdklab
2023-09-29  1:33 dpdklab
2023-09-29  1:32 dpdklab
2023-09-29  1:32 dpdklab
2023-09-29  1:32 dpdklab
2023-09-29  1:31 dpdklab
2023-09-29  1:30 dpdklab
2023-09-29  1:30 dpdklab
2023-09-29  1:30 dpdklab
2023-09-29  1:29 dpdklab
2023-09-29  1:29 dpdklab
2023-09-29  1:29 dpdklab
2023-09-29  1:29 dpdklab
2023-09-29  1:29 dpdklab
2023-09-29  1:29 dpdklab
2023-09-29  1:28 dpdklab
2023-09-29  1:28 dpdklab
2023-09-29  1:28 dpdklab
2023-09-29  1:28 dpdklab
2023-09-29  1:27 dpdklab
2023-09-29  1:27 dpdklab
2023-09-29  1:27 dpdklab
2023-09-29  1:27 dpdklab
2023-09-29  1:26 dpdklab
2023-09-29  1:26 dpdklab
2023-09-29  1:26 dpdklab
2023-09-29  1:25 dpdklab
2023-09-29  1:25 dpdklab
2023-09-29  1:25 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=6516281b.170a0220.969c5.1e0bSMTPIN_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).