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: |PENDING| [GIT MASTER] 3b017bdc4c25e2cd6733a9363e9c566b95834cc4
Date: Wed, 24 Jul 2024 06:59:26 -0700 (PDT)	[thread overview]
Message-ID: <66a108be.050a0220.30b12c.4be4SMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Performance Testing pending_

Branch: dpdk-next-net-intel

3b017bdc4c25e2cd6733a9363e9c566b95834cc4 --> performance testing pending

Upstream job id: Template-DTS-Pipeline#170396

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.6%                        |
+------------+---------+----------+-------------+------------------------------+
| 64         | 512     | 1        | 1           | -1.9%                        |
+------------+---------+----------+-------------+------------------------------+
| 64         | 2048    | 1        | 1           | 0.8%                         |
+------------+---------+----------+-------------+------------------------------+

Ubuntu 22.04 ARM
Kernel: 5.15.83+
Compiler: gcc 11.4.0
NIC: Arm Broadcom Inc. brcm_57414 25000 Mbps
Fail/Total: 0/1

Detail performance results: 
The measurement deltas are not ready yet! Please check back later.

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-07-24 13:59 UTC|newest]

Thread overview: 63+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-24 13:59 dpdklab [this message]
2024-07-24 17:18 dpdklab
2024-07-24 17:20 dpdklab
2024-07-24 17:24 dpdklab
2024-07-24 17:26 dpdklab
2024-07-24 17:27 dpdklab
2024-07-24 17:29 dpdklab
2024-07-24 17:31 dpdklab
2024-07-24 17:32 dpdklab
2024-07-24 17:32 dpdklab
2024-07-24 17:34 dpdklab
2024-07-24 17:35 dpdklab
2024-07-24 17:36 dpdklab
2024-07-24 17:36 dpdklab
2024-07-24 17:38 dpdklab
2024-07-24 17:38 dpdklab
2024-07-24 17:39 dpdklab
2024-07-24 17:39 dpdklab
2024-07-24 17:40 dpdklab
2024-07-24 17:40 dpdklab
2024-07-24 17:42 dpdklab
2024-07-24 17:43 dpdklab
2024-07-24 17:43 dpdklab
2024-07-24 17:45 dpdklab
2024-07-24 17:47 dpdklab
2024-07-24 17:47 dpdklab
2024-07-24 17:49 dpdklab
2024-07-24 17:49 dpdklab
2024-07-24 17:50 dpdklab
2024-07-24 17:53 dpdklab
2024-07-24 17:54 dpdklab
2024-07-24 17:54 dpdklab
2024-07-24 17:56 dpdklab
2024-07-24 17:56 dpdklab
2024-07-24 18:00 dpdklab
2024-07-24 18:03 dpdklab
2024-07-24 18:12 dpdklab
2024-07-24 18:21 dpdklab
2024-07-24 18:23 dpdklab
2024-07-24 18:24 dpdklab
2024-07-24 18:24 dpdklab
2024-07-24 18:25 dpdklab
2024-07-24 18:26 dpdklab
2024-07-24 18:27 dpdklab
2024-07-24 18:27 dpdklab
2024-07-24 18:28 dpdklab
2024-07-24 18:28 dpdklab
2024-07-24 18:30 dpdklab
2024-07-24 18:32 dpdklab
2024-07-24 18:32 dpdklab
2024-07-24 18:33 dpdklab
2024-07-24 18:35 dpdklab
2024-07-24 18:37 dpdklab
2024-07-24 18:41 dpdklab
2024-07-24 18:41 dpdklab
2024-07-24 18:43 dpdklab
2024-07-24 18:44 dpdklab
2024-07-24 18:44 dpdklab
2024-07-24 18:44 dpdklab
2024-07-24 18:47 dpdklab
2024-07-24 18:47 dpdklab
2024-07-24 18:56 dpdklab
2024-07-24 18:59 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=66a108be.050a0220.30b12c.4be4SMTPIN_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).