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
Subject: |SUCCESS| [GIT MASTER] 92d7ce4afc4a558f27bbc8368823c625f4e0f9dc
Date: Wed, 15 Nov 2023 04:47:05 -0800 (PST)	[thread overview]
Message-ID: <6554bdc9.170a0220.822b9.d467SMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Performance Testing PASS_

Branch: dpdk-next-eventdev

92d7ce4afc4a558f27bbc8368823c625f4e0f9dc --> performance testing pass

Test environment and result as below:

Ubuntu 22.04
Kernel: 5.15.0-78-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.2%                         |
+------------+---------+----------+-------------+------------------------------+
| 1024       | 256     | 1        | 1           | 0.1%                         |
+------------+---------+----------+-------------+------------------------------+
| 256        | 256     | 1        | 1           | 0.0%                         |
+------------+---------+----------+-------------+------------------------------+
| 1518       | 256     | 1        | 1           | -0.3%                        |
+------------+---------+----------+-------------+------------------------------+
| 512        | 256     | 1        | 1           | 0.0%                         |
+------------+---------+----------+-------------+------------------------------+

Ubuntu 22.04
Kernel: 5.15.0-78-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.1%                         |
+------------+---------+----------+-------------+------------------------------+
| 128        | 256     | 1        | 1           | 0.2%                         |
+------------+---------+----------+-------------+------------------------------+
| 1024       | 256     | 1        | 1           | 0.0%                         |
+------------+---------+----------+-------------+------------------------------+
| 256        | 256     | 1        | 1           | 0.2%                         |
+------------+---------+----------+-------------+------------------------------+
| 1518       | 256     | 1        | 1           | -0.0%                        |
+------------+---------+----------+-------------+------------------------------+
| 512        | 256     | 1        | 1           | -0.1%                        |
+------------+---------+----------+-------------+------------------------------+

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-11-15 12:47 UTC|newest]

Thread overview: 155+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-15 12:47 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-11-17  1:16 dpdklab
2023-11-17  0:57 dpdklab
2023-11-16 17:32 dpdklab
2023-11-16 17:14 dpdklab
2023-11-16 11:49 dpdklab
2023-11-16 11:43 dpdklab
2023-11-16  4:53 dpdklab
2023-11-16  2:36 dpdklab
2023-11-16  2:29 dpdklab
2023-11-16  2:25 dpdklab
2023-11-16  2:21 dpdklab
2023-11-16  2:21 dpdklab
2023-11-16  2:20 dpdklab
2023-11-16  2:17 dpdklab
2023-11-16  2:17 dpdklab
2023-11-16  2:17 dpdklab
2023-11-16  2:16 dpdklab
2023-11-16  2:16 dpdklab
2023-11-16  2:15 dpdklab
2023-11-16  2:14 dpdklab
2023-11-16  2:12 dpdklab
2023-11-16  2:12 dpdklab
2023-11-16  2:11 dpdklab
2023-11-16  2:11 dpdklab
2023-11-16  2:10 dpdklab
2023-11-16  2:10 dpdklab
2023-11-16  2:10 dpdklab
2023-11-16  2:10 dpdklab
2023-11-16  2:09 dpdklab
2023-11-16  2:09 dpdklab
2023-11-16  2:09 dpdklab
2023-11-16  2:09 dpdklab
2023-11-16  2:09 dpdklab
2023-11-16  2:09 dpdklab
2023-11-16  2:08 dpdklab
2023-11-16  2:08 dpdklab
2023-11-16  2:08 dpdklab
2023-11-16  2:07 dpdklab
2023-11-16  2:07 dpdklab
2023-11-16  2:07 dpdklab
2023-11-16  2:06 dpdklab
2023-11-16  2:06 dpdklab
2023-11-16  2:06 dpdklab
2023-11-16  2:05 dpdklab
2023-11-16  2:05 dpdklab
2023-11-16  2:04 dpdklab
2023-11-16  2:04 dpdklab
2023-11-16  2:03 dpdklab
2023-11-16  2:03 dpdklab
2023-11-16  2:03 dpdklab
2023-11-15 15:35 dpdklab
2023-11-15 13:59 dpdklab
2023-11-15 13:35 dpdklab
2023-11-15 13:31 dpdklab
2023-11-15 13:30 dpdklab
2023-11-15 13:24 dpdklab
2023-11-15 12:56 dpdklab
2023-11-15 12:55 dpdklab
2023-11-15 12:55 dpdklab
2023-11-15 12:52 dpdklab
2023-11-15 12:52 dpdklab
2023-11-15 12:50 dpdklab
2023-11-15 12:50 dpdklab
2023-11-15 12:49 dpdklab
2023-11-15 12:48 dpdklab
2023-11-15 12:48 dpdklab
2023-11-15 12:48 dpdklab
2023-11-15 12:47 dpdklab
2023-11-15 12:47 dpdklab
2023-11-15 12:47 dpdklab
2023-11-15 12:47 dpdklab
2023-11-15 12:47 dpdklab
2023-11-15 12:47 dpdklab
2023-11-15 12:46 dpdklab
2023-11-15 12:46 dpdklab
2023-11-15 12:46 dpdklab
2023-11-15 12:46 dpdklab
2023-11-15 12:46 dpdklab
2023-11-15 12:46 dpdklab
2023-11-15 12:46 dpdklab
2023-11-15 12:46 dpdklab
2023-11-15 12:45 dpdklab
2023-11-15 12:45 dpdklab
2023-11-15 12:45 dpdklab
2023-11-15 12:45 dpdklab
2023-11-15 12:45 dpdklab
2023-11-15 12:44 dpdklab
2023-11-15 12:44 dpdklab
2023-11-15 12:44 dpdklab
2023-11-15 12:44 dpdklab
2023-11-15 12:43 dpdklab
2023-11-15 12:43 dpdklab
2023-11-15 12:43 dpdklab
2023-11-15 12:43 dpdklab
2023-11-15 12:43 dpdklab
2023-11-15 12:42 dpdklab
2023-11-15 12:41 dpdklab
2023-11-15 12:41 dpdklab
2023-11-15 12:41 dpdklab
2023-11-15 12:41 dpdklab
2023-11-15 12:40 dpdklab
2023-11-15 12:40 dpdklab
2023-11-15  5:23 dpdklab
2023-11-15  3:29 dpdklab
2023-11-15  3:29 dpdklab
2023-11-15  3:03 dpdklab
2023-11-15  2:44 dpdklab
2023-11-15  2:43 dpdklab
2023-11-15  2:36 dpdklab
2023-11-15  2:35 dpdklab
2023-11-15  2:33 dpdklab
2023-11-15  2:32 dpdklab
2023-11-15  2:30 dpdklab
2023-11-15  2:29 dpdklab
2023-11-15  2:28 dpdklab
2023-11-15  2:28 dpdklab
2023-11-15  2:28 dpdklab
2023-11-15  2:28 dpdklab
2023-11-15  2:28 dpdklab
2023-11-15  2:27 dpdklab
2023-11-15  2:27 dpdklab
2023-11-15  2:27 dpdklab
2023-11-15  2:27 dpdklab
2023-11-15  2:26 dpdklab
2023-11-15  2:26 dpdklab
2023-11-15  2:26 dpdklab
2023-11-15  2:26 dpdklab
2023-11-15  2:25 dpdklab
2023-11-15  2:25 dpdklab
2023-11-15  2:25 dpdklab
2023-11-15  2:25 dpdklab
2023-11-15  2:24 dpdklab
2023-11-15  2:24 dpdklab
2023-11-15  2:24 dpdklab
2023-11-15  2:23 dpdklab
2023-11-15  2:23 dpdklab
2023-11-15  2:23 dpdklab
2023-11-15  2:22 dpdklab
2023-11-15  2:22 dpdklab
2023-11-15  2:21 dpdklab
2023-11-15  2:21 dpdklab
2023-11-15  2:20 dpdklab
2023-11-15  2:20 dpdklab
2023-11-15  2:20 dpdklab
2023-11-15  2:19 dpdklab
2023-11-15  2:19 dpdklab
2023-11-15  2:18 dpdklab
2023-11-15  2:18 dpdklab
2023-11-15  2:17 dpdklab
2023-11-15  2:17 dpdklab
2023-11-15  2:16 dpdklab
2023-11-15  2:15 dpdklab
2023-11-15  2:14 dpdklab
2023-11-15  2:13 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=6554bdc9.170a0220.822b9.d467SMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=alialnu@nvidia.com \
    --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).