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] c9df59bcc9bec67783de98486879594e52bdc418
Date: Mon, 29 May 2023 18:53:24 -0700 (PDT)	[thread overview]
Message-ID: <64755714.810a0220.5a574.3051SMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Performance Testing PASS_

Branch: dpdk

c9df59bcc9bec67783de98486879594e52bdc418 --> 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.1%                         |
+------------+---------+----------+-------------+------------------------------+
| 64         | 512     | 1        | 1           | 0.1%                         |
+------------+---------+----------+-------------+------------------------------+
| 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.0%                        |
+------------+---------+----------+-------------+------------------------------+

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-05-30  1:53 UTC|newest]

Thread overview: 237+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-30  1:53 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-06-09 23:00 dpdklab
2023-06-09 22:59 dpdklab
2023-06-09 22:50 dpdklab
2023-06-09 22:50 dpdklab
2023-06-09 22:50 dpdklab
2023-06-09 22:49 dpdklab
2023-06-09 22:45 dpdklab
2023-06-09 22:45 dpdklab
2023-06-09 22:45 dpdklab
2023-06-09 22:44 dpdklab
2023-06-09 22:44 dpdklab
2023-06-09 22:43 dpdklab
2023-06-09 22:43 dpdklab
2023-06-09 22:37 dpdklab
2023-06-08 22:35 dpdklab
2023-06-08 22:27 dpdklab
2023-06-08 22:27 dpdklab
2023-06-08 22:27 dpdklab
2023-06-08 22:27 dpdklab
2023-06-08 22:26 dpdklab
2023-06-08 22:26 dpdklab
2023-06-08 22:25 dpdklab
2023-06-01  1:53 dpdklab
2023-06-01  1:52 dpdklab
2023-06-01  1:48 dpdklab
2023-06-01  1:33 dpdklab
2023-06-01  1:22 dpdklab
2023-06-01  1:22 dpdklab
2023-06-01  1:10 dpdklab
2023-06-01  1:10 dpdklab
2023-06-01  1:03 dpdklab
2023-06-01  1:02 dpdklab
2023-06-01  1:02 dpdklab
2023-06-01  1:02 dpdklab
2023-06-01  0:57 dpdklab
2023-06-01  0:54 dpdklab
2023-05-31 17:23 dpdklab
2023-05-31 17:18 dpdklab
2023-05-31 17:15 dpdklab
2023-05-31 17:13 dpdklab
2023-05-31 17:09 dpdklab
2023-05-31 17:00 dpdklab
2023-05-31 15:59 dpdklab
2023-05-31 15:47 dpdklab
2023-05-31 15:41 dpdklab
2023-05-31 15:40 dpdklab
2023-05-31 15:39 dpdklab
2023-05-31 15:39 dpdklab
2023-05-31 15:39 dpdklab
2023-05-31 15:34 dpdklab
2023-05-31  2:02 dpdklab
2023-05-31  1:53 dpdklab
2023-05-31  1:37 dpdklab
2023-05-31  1:32 dpdklab
2023-05-31  1:28 dpdklab
2023-05-31  1:23 dpdklab
2023-05-31  1:10 dpdklab
2023-05-31  1:04 dpdklab
2023-05-31  1:04 dpdklab
2023-05-31  1:03 dpdklab
2023-05-31  1:02 dpdklab
2023-05-31  1:02 dpdklab
2023-05-31  0:57 dpdklab
2023-05-31  0:57 dpdklab
2023-05-30  4:05 dpdklab
2023-05-30  2:05 dpdklab
2023-05-30  2:04 dpdklab
2023-05-30  2:04 dpdklab
2023-05-30  2:04 dpdklab
2023-05-30  2:01 dpdklab
2023-05-30  1:46 dpdklab
2023-05-30  1:43 dpdklab
2023-05-30  1:39 dpdklab
2023-05-30  1:33 dpdklab
2023-05-30  1:31 dpdklab
2023-05-30  1:25 dpdklab
2023-05-30  1:24 dpdklab
2023-05-30  1:24 dpdklab
2023-05-30  1:23 dpdklab
2023-05-30  1:22 dpdklab
2023-05-30  1:10 dpdklab
2023-05-30  1:06 dpdklab
2023-05-30  1:03 dpdklab
2023-05-30  1:03 dpdklab
2023-05-30  1:03 dpdklab
2023-05-30  1:02 dpdklab
2023-05-30  1:02 dpdklab
2023-05-30  0:59 dpdklab
2023-05-30  0:59 dpdklab
2023-05-30  0:57 dpdklab
2023-05-30  0:57 dpdklab
2023-05-30  0:57 dpdklab
2023-05-29  4:03 dpdklab
2023-05-29  2:21 dpdklab
2023-05-29  2:21 dpdklab
2023-05-29  2:20 dpdklab
2023-05-29  2:17 dpdklab
2023-05-29  2:14 dpdklab
2023-05-29  2:08 dpdklab
2023-05-29  1:53 dpdklab
2023-05-29  1:52 dpdklab
2023-05-29  1:47 dpdklab
2023-05-29  1:40 dpdklab
2023-05-29  1:38 dpdklab
2023-05-29  1:34 dpdklab
2023-05-29  1:34 dpdklab
2023-05-29  1:29 dpdklab
2023-05-29  1:26 dpdklab
2023-05-29  1:24 dpdklab
2023-05-29  1:24 dpdklab
2023-05-29  1:23 dpdklab
2023-05-29  1:23 dpdklab
2023-05-29  1:22 dpdklab
2023-05-29  1:17 dpdklab
2023-05-29  1:10 dpdklab
2023-05-29  1:09 dpdklab
2023-05-29  1:04 dpdklab
2023-05-29  1:03 dpdklab
2023-05-29  1:02 dpdklab
2023-05-29  1:01 dpdklab
2023-05-29  0:56 dpdklab
2023-05-29  0:56 dpdklab
2023-05-28  4:03 dpdklab
2023-05-28  2:18 dpdklab
2023-05-28  2:08 dpdklab
2023-05-28  2:08 dpdklab
2023-05-28  2:02 dpdklab
2023-05-28  2:01 dpdklab
2023-05-28  2:01 dpdklab
2023-05-28  1:52 dpdklab
2023-05-28  1:48 dpdklab
2023-05-28  1:37 dpdklab
2023-05-28  1:37 dpdklab
2023-05-28  1:33 dpdklab
2023-05-28  1:32 dpdklab
2023-05-28  1:29 dpdklab
2023-05-28  1:28 dpdklab
2023-05-28  1:25 dpdklab
2023-05-28  1:23 dpdklab
2023-05-28  1:23 dpdklab
2023-05-28  1:22 dpdklab
2023-05-28  1:22 dpdklab
2023-05-28  1:10 dpdklab
2023-05-28  1:04 dpdklab
2023-05-28  1:03 dpdklab
2023-05-28  1:02 dpdklab
2023-05-28  1:02 dpdklab
2023-05-28  0:58 dpdklab
2023-05-28  0:57 dpdklab
2023-05-28  0:57 dpdklab
2023-05-27  4:21 dpdklab
2023-05-27  2:16 dpdklab
2023-05-27  2:15 dpdklab
2023-05-27  2:13 dpdklab
2023-05-27  2:06 dpdklab
2023-05-27  1:59 dpdklab
2023-05-27  1:58 dpdklab
2023-05-27  1:51 dpdklab
2023-05-27  1:46 dpdklab
2023-05-27  1:41 dpdklab
2023-05-27  1:40 dpdklab
2023-05-27  1:36 dpdklab
2023-05-27  1:32 dpdklab
2023-05-27  1:32 dpdklab
2023-05-27  1:30 dpdklab
2023-05-27  1:29 dpdklab
2023-05-27  1:29 dpdklab
2023-05-27  1:28 dpdklab
2023-05-27  1:22 dpdklab
2023-05-27  1:10 dpdklab
2023-05-27  1:10 dpdklab
2023-05-27  1:09 dpdklab
2023-05-27  1:04 dpdklab
2023-05-27  1:03 dpdklab
2023-05-27  1:02 dpdklab
2023-05-27  0:58 dpdklab
2023-05-27  0:57 dpdklab
2023-05-27  0:57 dpdklab
2023-05-26 10:46 dpdklab
2023-05-26 10:45 dpdklab
2023-05-26 10:05 dpdklab
2023-05-26  9:35 dpdklab
2023-05-26  9:14 dpdklab
2023-05-26  9:05 dpdklab
2023-05-26  8:35 dpdklab
2023-05-26  5:47 dpdklab
2023-05-26  4:06 dpdklab
2023-05-26  3:37 dpdklab
2023-05-26  3:34 dpdklab
2023-05-26  3:30 dpdklab
2023-05-26  3:28 dpdklab
2023-05-26  3:26 dpdklab
2023-05-26  3:22 dpdklab
2023-05-26  3:17 dpdklab
2023-05-26  3:12 dpdklab
2023-05-26  2:58 dpdklab
2023-05-26  2:45 dpdklab
2023-05-26  2:38 dpdklab
2023-05-26  1:41 dpdklab
2023-05-26  1:28 dpdklab
2023-05-26  1:17 dpdklab
2023-05-26  1:05 dpdklab
2023-05-26  1:05 dpdklab
2023-05-26  1:05 dpdklab
2023-05-26  1:04 dpdklab
2023-05-26  0:58 dpdklab
2023-05-25 20:53 dpdklab
2023-05-25 20:20 dpdklab
2023-05-25 20:14 dpdklab
2023-05-25 19:40 dpdklab
2023-05-25 19:35 dpdklab
2023-05-25 19:25 dpdklab
2023-05-25 19:21 dpdklab
2023-05-25 19:20 dpdklab
2023-05-25 19:16 dpdklab
2023-05-25 19:16 dpdklab
2023-05-25 19:12 dpdklab
2023-05-25 19:07 dpdklab
2023-05-25 19:02 dpdklab
2023-05-25 19:01 dpdklab
2023-05-25 18:56 dpdklab
2023-05-25 18:53 dpdklab
2023-05-25 18:53 dpdklab
2023-05-25 18:48 dpdklab
2023-05-25 18:45 dpdklab
2023-05-25 18:32 dpdklab
2023-05-25 18:28 dpdklab
2023-05-25 18:17 dpdklab
2023-05-25 18:15 dpdklab
2023-05-25 18:03 dpdklab
2023-05-25 17:50 dpdklab
2023-05-25 17:41 dpdklab
2023-05-25 17:40 dpdklab
2023-05-25 17:40 dpdklab
2023-05-25 17:39 dpdklab
2023-05-25 17:34 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=64755714.810a0220.5a574.3051SMTPIN_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).