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] 823f43b2c2c2af8bedb3ffaaadb1a41ddbb1e912
Date: Thu, 04 Jul 2024 00:33:02 -0700 (PDT)	[thread overview]
Message-ID: <6686502e.d40a0220.5cf6d.cc3fSMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Performance Testing pending_

Branch: dpdk-next-virtio

823f43b2c2c2af8bedb3ffaaadb1a41ddbb1e912 --> performance testing pending

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
Target: Unknown
Fail/Total: 0/4

Detail performance results: 
+----------+-------------+---------+------------+------------------------------+
| num_cpus | num_threads | txd/rxd | frame_size |  throughput difference from  |
|          |             |         |            |           expected           |
+==========+=============+=========+============+==============================+
| 1        | 2           | 512     | 64         | -0.5%                        |
+----------+-------------+---------+------------+------------------------------+
| 1        | 2           | 2048    | 64         | -0.6%                        |
+----------+-------------+---------+------------+------------------------------+
| 1        | 1           | 512     | 64         | 3.6%                         |
+----------+-------------+---------+------------+------------------------------+
| 1        | 1           | 2048    | 64         | -2.2%                        |
+----------+-------------+---------+------------+------------------------------+

22.04
Kernel: 5.15.0-94-generic
Compiler: gcc 11.4.0
NIC: Intel E810 100000 Mbps
Target: Unknown
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
Target: Unknown
Fail/Total: 0/6

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

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
Target: Unknown
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/29714/

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-07-04  7:33 UTC|newest]

Thread overview: 69+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-04  7:33 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-07-05  9:12 dpdklab
2024-07-05  8:59 dpdklab
2024-07-05  8:33 dpdklab
2024-07-05  8:21 dpdklab
2024-07-05  8:14 dpdklab
2024-07-05  8:12 dpdklab
2024-07-05  8:12 dpdklab
2024-07-05  8:07 dpdklab
2024-07-05  8:03 dpdklab
2024-07-05  8:02 dpdklab
2024-07-05  8:01 dpdklab
2024-07-05  8:00 dpdklab
2024-07-05  7:59 dpdklab
2024-07-05  7:59 dpdklab
2024-07-05  7:59 dpdklab
2024-07-05  7:57 dpdklab
2024-07-05  7:51 dpdklab
2024-07-05  7:48 dpdklab
2024-07-05  7:47 dpdklab
2024-07-05  7:46 dpdklab
2024-07-05  7:44 dpdklab
2024-07-05  7:43 dpdklab
2024-07-05  7:42 dpdklab
2024-07-05  7:38 dpdklab
2024-07-05  7:33 dpdklab
2024-07-05  7:31 dpdklab
2024-07-05  7:29 dpdklab
2024-07-05  7:29 dpdklab
2024-07-05  7:28 dpdklab
2024-07-05  7:27 dpdklab
2024-07-05  7:02 dpdklab
2024-07-05  6:58 dpdklab
2024-07-05  6:56 dpdklab
2024-07-05  6:51 dpdklab
2024-07-05  6:45 dpdklab
2024-07-05  6:33 dpdklab
2024-07-05  6:28 dpdklab
2024-07-05  6:25 dpdklab
2024-07-05  6:09 dpdklab
2024-07-05  5:53 dpdklab
2024-07-05  5:50 dpdklab
2024-07-05  5:15 dpdklab
2024-07-05  5:10 dpdklab
2024-07-05  4:50 dpdklab
2024-07-05  4:46 dpdklab
2024-07-05  4:40 dpdklab
2024-07-05  4:37 dpdklab
2024-07-05  4:33 dpdklab
2024-07-05  4:29 dpdklab
2024-07-05  4:26 dpdklab
2024-07-05  4:18 dpdklab
2024-07-05  3:58 dpdklab
2024-07-05  3:42 dpdklab
2024-07-05  3:39 dpdklab
2024-07-05  3:31 dpdklab
2024-07-05  3:28 dpdklab
2024-07-05  3:27 dpdklab
2024-07-05  3:21 dpdklab
2024-07-05  3:19 dpdklab
2024-07-05  3:03 dpdklab
2024-07-05  2:33 dpdklab
2024-07-04 20:50 dpdklab
2024-07-04 18:51 dpdklab
2024-07-04 18:42 dpdklab
2024-07-04 18:42 dpdklab
2024-07-04 18:37 dpdklab
2024-07-04 18:36 dpdklab
2024-07-04  7:27 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=6686502e.d40a0220.5cf6d.cc3fSMTPIN_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).