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] a3d2c6974f915eb9cb3d015afdc4cc72537a6159
Date: Tue, 10 Oct 2023 19:43:26 -0700 (PDT)	[thread overview]
Message-ID: <65260bce.170a0220.a321a.5d47SMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Performance Testing PASS_

Branch: dpdk

a3d2c6974f915eb9cb3d015afdc4cc72537a6159 --> 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-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.0%                        |
+------------+---------+----------+-------------+------------------------------+
| 128        | 256     | 1        | 1           | 0.0%                         |
+------------+---------+----------+-------------+------------------------------+
| 1024       | 256     | 1        | 1           | 0.0%                         |
+------------+---------+----------+-------------+------------------------------+
| 256        | 256     | 1        | 1           | -0.1%                        |
+------------+---------+----------+-------------+------------------------------+
| 1518       | 256     | 1        | 1           | 0.2%                         |
+------------+---------+----------+-------------+------------------------------+
| 512        | 256     | 1        | 1           | -0.5%                        |
+------------+---------+----------+-------------+------------------------------+

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-10-11  2:43 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-11  2:43 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-10-12 15:10 dpdklab
2023-10-12  8:05 dpdklab
2023-10-12  7:56 dpdklab
2023-10-12  7:28 dpdklab
2023-10-12  7:26 dpdklab
2023-10-11 14:27 dpdklab
2023-10-11 10:52 dpdklab
2023-10-11 10:41 dpdklab
2023-10-11 10:40 dpdklab
2023-10-11 10:13 dpdklab
2023-10-11 10:07 dpdklab
2023-10-11  9:46 dpdklab
2023-10-11  9:46 dpdklab
2023-10-11  9:46 dpdklab
2023-10-11  9:46 dpdklab
2023-10-11  9:45 dpdklab
2023-10-11  9:44 dpdklab
2023-10-11  9:43 dpdklab
2023-10-11  9:42 dpdklab
2023-10-11  9:42 dpdklab
2023-10-11  9:38 dpdklab
2023-10-11  9:38 dpdklab
2023-10-11  9:38 dpdklab
2023-10-11  9:38 dpdklab
2023-10-11  9:37 dpdklab
2023-10-11  9:37 dpdklab
2023-10-11  9:37 dpdklab
2023-10-11  9:36 dpdklab
2023-10-11  9:34 dpdklab
2023-10-11  9:33 dpdklab
2023-10-11  9:32 dpdklab
2023-10-11  9:29 dpdklab
2023-10-11  9:14 dpdklab
2023-10-11  9:09 dpdklab
2023-10-11  9:06 dpdklab
2023-10-11  9:05 dpdklab
2023-10-11  8:56 dpdklab
2023-10-11  8:54 dpdklab
2023-10-11  8:54 dpdklab
2023-10-11  8:49 dpdklab
2023-10-11  8:47 dpdklab
2023-10-11  8:46 dpdklab
2023-10-11  8:45 dpdklab
2023-10-11  8:44 dpdklab
2023-10-11  8:44 dpdklab
2023-10-11  8:43 dpdklab
2023-10-11  3:03 dpdklab
2023-10-11  2:41 dpdklab
2023-10-11  2:34 dpdklab
2023-10-11  2:30 dpdklab
2023-10-11  2:30 dpdklab
2023-10-11  2:28 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=65260bce.170a0220.a321a.5d47SMTPIN_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).