automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>, Ali Alnubani <alialnu@nvidia.com>
Cc: dpdk-test-reports@iol.unh.edu,
	Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>,
	Ferruh Yigit <ferruh.yigit@amd.com>
Subject: |SUCCESS| [GIT MASTER] 78d0246a2e2fb14cba220d507192d12d2ce896ac
Date: Tue, 17 Dec 2024 00:47:14 -0800 (PST)	[thread overview]
Message-ID: <67613a92.170a0220.56681.61a2SMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Performance Testing PASS_

Branch: dpdk-next-net

78d0246a2e2fb14cba220d507192d12d2ce896ac --> performance testing pass

Upstream job id: Template-DTS-Pipeline#202757

Test environment and result as below:

Ubuntu 24.04
Kernel: 6.8.0-45-generic
Compiler: gcc 13.2.0
NIC: Mellanox ConnectX-6 Lx 25000 Mbps
Fail/Total: 0/6

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

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-12-17  8:47 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-17  8:47 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-12-18  8:51 dpdklab
2024-12-18  6:49 dpdklab
2024-12-18  5:51 dpdklab
2024-12-18  3:17 dpdklab
2024-12-18  3:12 dpdklab
2024-12-18  3:11 dpdklab
2024-12-18  2:58 dpdklab
2024-12-18  2:55 dpdklab
2024-12-18  2:43 dpdklab
2024-12-18  1:10 dpdklab
2024-12-18  1:10 dpdklab
2024-12-18  0:31 dpdklab
2024-12-18  0:29 dpdklab
2024-12-18  0:10 dpdklab
2024-12-17 23:52 dpdklab
2024-12-17 23:22 dpdklab
2024-12-17 23:20 dpdklab
2024-12-17 23:04 dpdklab
2024-12-17 23:00 dpdklab
2024-12-17 22:55 dpdklab
2024-12-17 22:53 dpdklab
2024-12-17 22:50 dpdklab
2024-12-17 22:49 dpdklab
2024-12-17 22:40 dpdklab
2024-12-17 22:23 dpdklab
2024-12-17 22:20 dpdklab
2024-12-17 22:19 dpdklab
2024-12-17 22:13 dpdklab
2024-12-17 21:59 dpdklab
2024-12-17 21:54 dpdklab
2024-12-17 21:38 dpdklab
2024-12-17 21:37 dpdklab
2024-12-17 21:36 dpdklab
2024-12-17 21:35 dpdklab
2024-12-17 21:25 dpdklab
2024-12-17 13:16 dpdklab
2024-12-17 13:12 dpdklab
2024-12-17 12:21 dpdklab
2024-12-17 11:48 dpdklab
2024-12-17 11:34 dpdklab
2024-12-17 10:43 dpdklab
2024-12-17 10:41 dpdklab
2024-12-17 10:21 dpdklab
2024-12-17 10:20 dpdklab
2024-12-17  9:55 dpdklab
2024-12-17  9:53 dpdklab
2024-12-17  9:45 dpdklab
2024-12-17  9:44 dpdklab
2024-12-17  9:28 dpdklab
2024-12-17  9:25 dpdklab
2024-12-17  9:16 dpdklab
2024-12-17  8:51 dpdklab
2024-12-17  8:44 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=67613a92.170a0220.56681.61a2SMTPIN_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).