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] d08a322d92550214304855ae392097cc5a71d631
Date: Fri, 19 Jul 2024 23:40:45 -0700 (PDT)	[thread overview]
Message-ID: <669b5bed.810a0220.245355.4f57SMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Performance Testing pending_

Branch: dpdk-next-net

d08a322d92550214304855ae392097cc5a71d631 --> performance testing pending

Upstream job id: Template-DTS-Pipeline#169274

Test environment and result as below:

Ubuntu 20.04
Kernel: 5.4.0-122-generic
Compiler: gcc 9.4.0
NIC: Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Fail/Total: 0/1

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

Ubuntu 20.04
Kernel: 5.4.0-122-generic
Compiler: gcc 9.4.0
NIC: Intel Corporation Ethernet Converged Network Adapter 82599ES 10000 Mbps
Fail/Total: 0/1

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

Ubuntu 20.04 ARM
Kernel: 5.15.0-97-generic
Compiler: gcc 11.4.0
NIC: Arm Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 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.3%                         |
+------------+---------+----------+-------------+------------------------------+

22.04
Kernel: 5.15.0-94-generic
Compiler: gcc 11.4.0
NIC: Intel E810 100000 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/29925/

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-07-20  7:34 UTC|newest]

Thread overview: 60+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-20  6:40 dpdklab [this message]
2024-07-20  6:50 dpdklab
2024-07-20  6:51 dpdklab
2024-07-20  6:52 dpdklab
2024-07-20  6:52 dpdklab
2024-07-20  6:53 dpdklab
2024-07-20  6:55 dpdklab
2024-07-20  6:56 dpdklab
2024-07-20  6:59 dpdklab
2024-07-20  7:01 dpdklab
2024-07-20  7:01 dpdklab
2024-07-20  7:02 dpdklab
2024-07-20  7:04 dpdklab
2024-07-20  7:05 dpdklab
2024-07-20  7:05 dpdklab
2024-07-20  7:06 dpdklab
2024-07-20  7:07 dpdklab
2024-07-20  7:07 dpdklab
2024-07-20  7:10 dpdklab
2024-07-20  7:10 dpdklab
2024-07-20  7:11 dpdklab
2024-07-20  7:12 dpdklab
2024-07-20  7:12 dpdklab
2024-07-20  7:12 dpdklab
2024-07-20  7:13 dpdklab
2024-07-20  7:14 dpdklab
2024-07-20  7:14 dpdklab
2024-07-20  7:14 dpdklab
2024-07-20  7:14 dpdklab
2024-07-20  7:15 dpdklab
2024-07-20  7:15 dpdklab
2024-07-20  7:18 dpdklab
2024-07-20  7:18 dpdklab
2024-07-20  7:20 dpdklab
2024-07-20  7:21 dpdklab
2024-07-20  7:21 dpdklab
2024-07-20  7:22 dpdklab
2024-07-20  7:23 dpdklab
2024-07-20  7:23 dpdklab
2024-07-20  7:24 dpdklab
2024-07-20  7:25 dpdklab
2024-07-20  7:25 dpdklab
2024-07-20  7:25 dpdklab
2024-07-20  7:26 dpdklab
2024-07-20  7:27 dpdklab
2024-07-20  7:28 dpdklab
2024-07-20  7:31 dpdklab
2024-07-20  7:32 dpdklab
2024-07-20  7:32 dpdklab
2024-07-20  7:32 dpdklab
2024-07-20  7:34 dpdklab
2024-07-20  7:35 dpdklab
2024-07-20  7:38 dpdklab
2024-07-20  7:39 dpdklab
2024-07-20  7:40 dpdklab
2024-07-20  7:41 dpdklab
2024-07-20  7:42 dpdklab
2024-07-20  7:43 dpdklab
2024-07-20  8:15 dpdklab
2024-07-20  8:32 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=669b5bed.810a0220.245355.4f57SMTPIN_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).