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] 4358da71b382d1015be7323e1b48d15e34f2562b
Date: Sat, 25 Nov 2023 18:17:25 -0800 (PST)	[thread overview]
Message-ID: <6562aab5.9f0a0220.d5b29.1a33SMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Performance Testing PASS_

Branch: dpdk

4358da71b382d1015be7323e1b48d15e34f2562b --> 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.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.0%                         |
+------------+---------+----------+-------------+------------------------------+
| 64         | 2048    | 1        | 1           | 0.1%                         |
+------------+---------+----------+-------------+------------------------------+

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-11-26  2:17 UTC|newest]

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