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, Akhil Goyal <gakhil@marvell.com>
Subject: |SUCCESS| [GIT MASTER] 7df61db6c387703a36306c1aea92225921e2eeb2
Date: Wed, 18 Dec 2024 12:41:26 -0800 (PST)	[thread overview]
Message-ID: <67633376.050a0220.282cf.b5fdSMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Performance Testing PASS_

Branch: dpdk-next-crypto

7df61db6c387703a36306c1aea92225921e2eeb2 --> performance testing pass

Upstream job id: Template-DTS-Pipeline#203162

Test environment and result as below:

Ubuntu 22.04
Kernel: 5.15.0-100-generic
Compiler: gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
NIC: Broadcom Inc. and subsidiaries BCM57414 NetXtreme-E 10Gb/25Gb RDMA Ethernet Controller 16d7 25 Mbps
Fail/Total: 0/3

Detail performance results: 
+------------+---------+----------+-------------+------------------------------+
| frame_size | txd/rxd | num_cpus | num_threads |  throughput difference from  |
|            |         |          |             |           expected           |
+============+=========+==========+=============+==============================+
| 64         | 128     | 1        | 1           | -0.8%                        |
+------------+---------+----------+-------------+------------------------------+
| 64         | 512     | 1        | 1           | -1.4%                        |
+------------+---------+----------+-------------+------------------------------+
| 64         | 2048    | 1        | 1           | 0.3%                         |
+------------+---------+----------+-------------+------------------------------+

Ubuntu 22.04 ARM
Kernel: 5.15.83+
Compiler: gcc 11.4.0
NIC: Arm Broadcom Inc. brcm_57414 25000 Mbps
Fail/Total: 0/2

Detail performance results: 
+------------+---------+----------+-------------+------------------------------+
| frame_size | txd/rxd | num_cpus | num_threads |  throughput difference from  |
|            |         |          |             |           expected           |
+============+=========+==========+=============+==============================+
| 64         | 512     | 1        | 1           | -0.1%                        |
+------------+---------+----------+-------------+------------------------------+
| 64         | 2048    | 1        | 1           | -0.4%                        |
+------------+---------+----------+-------------+------------------------------+

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-12-18 20:41 UTC|newest]

Thread overview: 104+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-18 20:41 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-12-19  2:19 dpdklab
2024-12-18 23:34 dpdklab
2024-12-18 22:21 dpdklab
2024-12-18 21:50 dpdklab
2024-12-18 21:39 dpdklab
2024-12-18 21:17 dpdklab
2024-12-18 21:14 dpdklab
2024-12-18 20:59 dpdklab
2024-12-18 20:47 dpdklab
2024-12-14 21:56 dpdklab
2024-12-14 19:47 dpdklab
2024-12-14 16:16 dpdklab
2024-12-14 15:22 dpdklab
2024-12-14 13:53 dpdklab
2024-12-14 13:04 dpdklab
2024-12-14 12:34 dpdklab
2024-12-14 12:33 dpdklab
2024-12-14 11:39 dpdklab
2024-12-14 10:51 dpdklab
2024-12-14 10:21 dpdklab
2024-12-14  9:15 dpdklab
2024-12-14  9:10 dpdklab
2024-12-14  9:00 dpdklab
2024-12-14  8:36 dpdklab
2024-12-13 22:26 dpdklab
2024-12-13 22:05 dpdklab
2024-12-13 21:54 dpdklab
2024-12-13 21:02 dpdklab
2024-12-13 20:04 dpdklab
2024-12-13 20:02 dpdklab
2024-12-13 18:10 dpdklab
2024-12-13 15:53 dpdklab
2024-12-13 11:52 dpdklab
2024-12-13 10:44 dpdklab
2024-12-13 10:07 dpdklab
2024-12-13 10:04 dpdklab
2024-12-13  9:47 dpdklab
2024-12-13  9:40 dpdklab
2024-12-13  9:33 dpdklab
2024-12-13  9:27 dpdklab
2024-12-10  3:31 dpdklab
2024-12-10  2:09 dpdklab
2024-12-10  2:06 dpdklab
2024-12-10  1:54 dpdklab
2024-12-10  1:50 dpdklab
2024-12-10  1:49 dpdklab
2024-12-10  1:44 dpdklab
2024-12-10  1:42 dpdklab
2024-12-10  1:40 dpdklab
2024-12-10  1:40 dpdklab
2024-12-10  1:32 dpdklab
2024-12-10  1:29 dpdklab
2024-12-10  1:23 dpdklab
2024-12-08  3:22 dpdklab
2024-12-08  2:08 dpdklab
2024-12-08  2:05 dpdklab
2024-12-08  1:49 dpdklab
2024-12-08  1:48 dpdklab
2024-12-08  1:47 dpdklab
2024-12-08  1:43 dpdklab
2024-12-08  1:40 dpdklab
2024-12-08  1:39 dpdklab
2024-12-08  1:31 dpdklab
2024-12-08  1:30 dpdklab
2024-12-08  1:23 dpdklab
2024-12-06  4:23 dpdklab
2024-12-06  2:02 dpdklab
2024-12-06  2:00 dpdklab
2024-12-06  1:59 dpdklab
2024-12-06  1:50 dpdklab
2024-12-06  1:48 dpdklab
2024-12-06  1:45 dpdklab
2024-12-06  1:43 dpdklab
2024-12-06  1:40 dpdklab
2024-12-06  1:39 dpdklab
2024-12-06  1:32 dpdklab
2024-12-06  1:31 dpdklab
2024-12-06  0:33 dpdklab
2024-12-05 22:27 dpdklab
2024-12-05 21:56 dpdklab
2024-12-05 21:44 dpdklab
2024-12-05 21:37 dpdklab
2024-12-05 21:35 dpdklab
2024-12-05 21:33 dpdklab
2024-12-05 21:30 dpdklab
2024-12-05 21:29 dpdklab
2024-12-05 21:26 dpdklab
2024-12-05 21:25 dpdklab
2024-12-05 21:17 dpdklab
2024-12-05 21:09 dpdklab
2024-12-05 21:09 dpdklab
2024-12-04 21:19 dpdklab
2024-12-04 20:05 dpdklab
2024-12-04 20:03 dpdklab
2024-12-04 19:57 dpdklab
2024-12-04 19:51 dpdklab
2024-12-04 19:42 dpdklab
2024-12-04 19:34 dpdklab
2024-12-04 19:34 dpdklab
2024-12-04 19:31 dpdklab
2024-12-04 19:30 dpdklab
2024-12-04 19:22 dpdklab
2024-12-04 19:17 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=67633376.050a0220.282cf.b5fdSMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=gakhil@marvell.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).