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, Xueming Li <xuemingl@nvidia.com>,
	Christian Ehrhardt <christian.ehrhardt@canonical.com>,
	Kevin Traynor <ktraynor@redhat.com>,
	Luca Boccassi <bluca@debian.org>
Subject: |SUCCESS| [GIT MASTER] 97cdb0db6d1315eed07751218a80f078c4869f4e
Date: Mon, 11 Dec 2023 04:06:20 -0800 (PST)	[thread overview]
Message-ID: <6576fb3c.170a0220.3a048.7d0aSMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Performance Testing PASS_

Branch: 22.11-staging

97cdb0db6d1315eed07751218a80f078c4869f4e --> 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.6%                        |
+----------+-------------+---------+------------+------------------------------+
| 1        | 2           | 2048    | 64         | -0.2%                        |
+----------+-------------+---------+------------+------------------------------+
| 1        | 1           | 512     | 64         | -1.7%                        |
+----------+-------------+---------+------------+------------------------------+
| 1        | 1           | 2048    | 64         | 1.5%                         |
+----------+-------------+---------+------------+------------------------------+

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

UNH-IOL DPDK Community Lab

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

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

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-11 12:06 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-12-11 15:41 dpdklab
2023-12-11 15:39 dpdklab
2023-12-11 15:11 dpdklab
2023-12-11 13:44 dpdklab
2023-12-11 13:38 dpdklab
2023-12-11 13:26 dpdklab
2023-12-11 13:08 dpdklab
2023-12-11 12:57 dpdklab
2023-12-11 12:56 dpdklab
2023-12-11 12:55 dpdklab
2023-12-11 12:54 dpdklab
2023-12-11 12:34 dpdklab
2023-12-11 12:30 dpdklab
2023-12-11 12:26 dpdklab
2023-12-11 12:25 dpdklab
2023-12-11 12:25 dpdklab
2023-12-11 12:25 dpdklab
2023-12-11 12:23 dpdklab
2023-12-11 12:22 dpdklab
2023-12-11 12:22 dpdklab
2023-12-11 12:18 dpdklab
2023-12-11 12:15 dpdklab
2023-12-11 12:13 dpdklab
2023-12-11 12:12 dpdklab
2023-12-11 12:10 dpdklab
2023-12-11 12:09 dpdklab
2023-12-11 12:02 dpdklab
2023-12-11 11:59 dpdklab
2023-12-11 11:57 dpdklab
2023-12-11 11:56 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=6576fb3c.170a0220.3a048.7d0aSMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=bluca@debian.org \
    --cc=christian.ehrhardt@canonical.com \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=ktraynor@redhat.com \
    --cc=test-report@dpdk.org \
    --cc=xuemingl@nvidia.com \
    /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).