automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Ali Alnubani <alialnu@nvidia.com>, Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu,
	Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>,
	Ferruh Yigit <ferruh.yigit@amd.com>
Subject: |SUCCESS| [GIT MASTER] ded4d4765171b88470e59307f10625e942f22fca
Date: Wed, 27 Mar 2024 00:51:19 -0700 (PDT)	[thread overview]
Message-ID: <6603cff7.050a0220.94dbc.b720SMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Performance Testing PASS_

Branch: dpdk-next-net

ded4d4765171b88470e59307f10625e942f22fca --> performance testing pass

Test environment and result as below:

Ubuntu 22.04
Kernel: 5.15.0-94-generic
Compiler: gcc 11.4.0
NIC: Mellanox ConnectX-5 100000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/6

Detail performance results: 
+------------+---------+----------+-------------+------------------------------+
| frame_size | txd/rxd | num_cpus | num_threads |  throughput difference from  |
|            |         |          |             |           expected           |
+============+=========+==========+=============+==============================+
| 64         | 256     | 1        | 1           | 0.2%                         |
+------------+---------+----------+-------------+------------------------------+
| 128        | 256     | 1        | 1           | 0.1%                         |
+------------+---------+----------+-------------+------------------------------+
| 1024       | 256     | 1        | 1           | -0.1%                        |
+------------+---------+----------+-------------+------------------------------+
| 256        | 256     | 1        | 1           | 0.0%                         |
+------------+---------+----------+-------------+------------------------------+
| 1518       | 256     | 1        | 1           | -0.1%                        |
+------------+---------+----------+-------------+------------------------------+
| 512        | 256     | 1        | 1           | -0.3%                        |
+------------+---------+----------+-------------+------------------------------+

Ubuntu 22.04
Kernel: 5.15.0-94-generic
Compiler: gcc 11.4.0
NIC: Mellanox ConnectX-6 Lx 25000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/6

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

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-03-27  7:51 UTC|newest]

Thread overview: 78+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-27  7:51 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-04-02  6:49 dpdklab
2024-04-02  6:29 dpdklab
2024-04-02  6:25 dpdklab
2024-04-02  6:21 dpdklab
2024-04-02  6:17 dpdklab
2024-03-27 11:33 dpdklab
2024-03-27 11:05 dpdklab
2024-03-27 10:51 dpdklab
2024-03-27 10:16 dpdklab
2024-03-27  9:58 dpdklab
2024-03-27  9:16 dpdklab
2024-03-27  9:15 dpdklab
2024-03-27  9:15 dpdklab
2024-03-27  9:13 dpdklab
2024-03-27  9:11 dpdklab
2024-03-27  9:10 dpdklab
2024-03-27  9:10 dpdklab
2024-03-27  9:09 dpdklab
2024-03-27  9:09 dpdklab
2024-03-27  9:08 dpdklab
2024-03-27  9:08 dpdklab
2024-03-27  9:07 dpdklab
2024-03-27  9:07 dpdklab
2024-03-27  9:07 dpdklab
2024-03-27  9:06 dpdklab
2024-03-27  9:06 dpdklab
2024-03-27  9:06 dpdklab
2024-03-27  9:05 dpdklab
2024-03-27  9:05 dpdklab
2024-03-27  9:05 dpdklab
2024-03-27  9:05 dpdklab
2024-03-27  9:04 dpdklab
2024-03-27  9:04 dpdklab
2024-03-27  9:04 dpdklab
2024-03-27  9:04 dpdklab
2024-03-27  9:03 dpdklab
2024-03-27  9:03 dpdklab
2024-03-27  9:03 dpdklab
2024-03-27  9:03 dpdklab
2024-03-27  9:03 dpdklab
2024-03-27  9:02 dpdklab
2024-03-27  9:02 dpdklab
2024-03-27  9:02 dpdklab
2024-03-27  9:01 dpdklab
2024-03-27  9:00 dpdklab
2024-03-27  8:59 dpdklab
2024-03-27  8:58 dpdklab
2024-03-27  8:57 dpdklab
2024-03-27  8:57 dpdklab
2024-03-27  8:55 dpdklab
2024-03-27  8:55 dpdklab
2024-03-27  8:54 dpdklab
2024-03-27  8:53 dpdklab
2024-03-27  8:52 dpdklab
2024-03-27  8:47 dpdklab
2024-03-27  8:46 dpdklab
2024-03-27  8:45 dpdklab
2024-03-27  8:39 dpdklab
2024-03-27  8:35 dpdklab
2024-03-27  8:35 dpdklab
2024-03-27  7:59 dpdklab
2024-03-27  7:59 dpdklab
2024-03-27  7:58 dpdklab
2024-03-27  7:58 dpdklab
2024-03-27  7:58 dpdklab
2024-03-27  7:57 dpdklab
2024-03-27  7:57 dpdklab
2024-03-27  7:53 dpdklab
2024-03-27  7:52 dpdklab
2024-03-27  7:49 dpdklab
2024-03-27  7:38 dpdklab
2024-03-27  7:37 dpdklab
2024-03-27  7:36 dpdklab
2024-03-27  7:31 dpdklab
2024-03-27  7:30 dpdklab
2024-03-27  7:13 dpdklab
2024-03-27  7:07 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=6603cff7.050a0220.94dbc.b720SMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=alialnu@nvidia.com \
    --cc=andrew.rybchenko@oktetlabs.ru \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=ferruh.yigit@amd.com \
    --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).