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] 31e60e81f025e9fffa69b68bffe5cfaa22d5c098
Date: Tue, 19 Sep 2023 18:12:23 -0700 (PDT)	[thread overview]
Message-ID: <650a46f7.170a0220.d802d.1aafSMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Performance Testing PASS_

Branch: dpdk

31e60e81f025e9fffa69b68bffe5cfaa22d5c098 --> performance testing pass

Test environment and result as below:

Ubuntu 20.04
Kernel: 4.15.0-generic
Compiler: gcc 7.4
NIC: Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/4

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

Ubuntu 20.04
Kernel: 4.15.0-generic
Compiler: gcc 7.4
NIC: Intel Corporation Ethernet Converged Network Adapter 82599ES 10000 Mbps
Target: x86_64-native-linuxapp-gcc
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.0%                        |
+----------+-------------+---------+------------+------------------------------+
| 1        | 1           | 128     | 64         | 0.3%                         |
+----------+-------------+---------+------------+------------------------------+
| 1        | 1           | 512     | 64         | 0.4%                         |
+----------+-------------+---------+------------+------------------------------+
| 1        | 1           | 2048    | 64         | -0.3%                        |
+----------+-------------+---------+------------+------------------------------+

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-09-20  1:12 UTC|newest]

Thread overview: 90+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-20  1:12 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-09-21 19:28 dpdklab
2023-09-21 19:14 dpdklab
2023-09-21 19:12 dpdklab
2023-09-21 19:09 dpdklab
2023-09-21  2:25 dpdklab
2023-09-21  1:36 dpdklab
2023-09-21  1:33 dpdklab
2023-09-21  1:30 dpdklab
2023-09-21  1:28 dpdklab
2023-09-21  1:26 dpdklab
2023-09-21  1:24 dpdklab
2023-09-21  1:22 dpdklab
2023-09-21  1:21 dpdklab
2023-09-21  1:21 dpdklab
2023-09-21  1:18 dpdklab
2023-09-21  1:18 dpdklab
2023-09-21  1:18 dpdklab
2023-09-21  1:17 dpdklab
2023-09-21  1:15 dpdklab
2023-09-21  1:14 dpdklab
2023-09-21  1:14 dpdklab
2023-09-21  1:13 dpdklab
2023-09-21  1:11 dpdklab
2023-09-21  1:11 dpdklab
2023-09-21  1:11 dpdklab
2023-09-21  1:10 dpdklab
2023-09-21  1:10 dpdklab
2023-09-21  1:10 dpdklab
2023-09-21  1:10 dpdklab
2023-09-21  1:10 dpdklab
2023-09-21  1:09 dpdklab
2023-09-21  1:09 dpdklab
2023-09-21  1:09 dpdklab
2023-09-21  1:08 dpdklab
2023-09-21  1:08 dpdklab
2023-09-21  1:07 dpdklab
2023-09-21  1:06 dpdklab
2023-09-21  1:06 dpdklab
2023-09-21  1:06 dpdklab
2023-09-21  1:06 dpdklab
2023-09-21  1:05 dpdklab
2023-09-21  1:05 dpdklab
2023-09-21  1:05 dpdklab
2023-09-21  1:05 dpdklab
2023-09-21  1:05 dpdklab
2023-09-21  1:04 dpdklab
2023-09-21  1:04 dpdklab
2023-09-20  2:28 dpdklab
2023-09-20  1:44 dpdklab
2023-09-20  1:43 dpdklab
2023-09-20  1:41 dpdklab
2023-09-20  1:37 dpdklab
2023-09-20  1:33 dpdklab
2023-09-20  1:31 dpdklab
2023-09-20  1:27 dpdklab
2023-09-20  1:27 dpdklab
2023-09-20  1:26 dpdklab
2023-09-20  1:22 dpdklab
2023-09-20  1:21 dpdklab
2023-09-20  1:20 dpdklab
2023-09-20  1:19 dpdklab
2023-09-20  1:18 dpdklab
2023-09-20  1:18 dpdklab
2023-09-20  1:15 dpdklab
2023-09-20  1:13 dpdklab
2023-09-20  1:13 dpdklab
2023-09-20  1:13 dpdklab
2023-09-20  1:12 dpdklab
2023-09-20  1:12 dpdklab
2023-09-20  1:10 dpdklab
2023-09-20  1:10 dpdklab
2023-09-20  1:10 dpdklab
2023-09-20  1:10 dpdklab
2023-09-20  1:09 dpdklab
2023-09-20  1:09 dpdklab
2023-09-20  1:08 dpdklab
2023-09-20  1:08 dpdklab
2023-09-20  1:08 dpdklab
2023-09-20  1:07 dpdklab
2023-09-20  1:07 dpdklab
2023-09-20  1:07 dpdklab
2023-09-20  1:06 dpdklab
2023-09-20  1:06 dpdklab
2023-09-20  1:06 dpdklab
2023-09-20  1:06 dpdklab
2023-09-20  1:06 dpdklab
2023-09-20  1:05 dpdklab
2023-09-20  1:05 dpdklab
2023-09-20  1:05 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=650a46f7.170a0220.d802d.1aafSMTPIN_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).