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, Jerin Jacob <jerinj@marvell.com>
Subject: |SUCCESS| [GIT MASTER] 1b3bf1128d9bda5595861814792f74b8f57160c8
Date: Tue, 17 Dec 2024 15:31:01 -0800 (PST)	[thread overview]
Message-ID: <676209b5.050a0220.1f8fec.84b6SMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Performance Testing PASS_

Branch: dpdk-next-eventdev

1b3bf1128d9bda5595861814792f74b8f57160c8 --> performance testing pass

Upstream job id: Template-DTS-Pipeline#202890

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.3%                         |
+------------+---------+----------+-------------+------------------------------+
| 64         | 512     | 1        | 1           | 0.1%                         |
+------------+---------+----------+-------------+------------------------------+
| 64         | 2048    | 1        | 1           | -0.8%                        |
+------------+---------+----------+-------------+------------------------------+

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.2%                         |
+------------+---------+----------+-------------+------------------------------+
| 64         | 2048    | 1        | 1           | 0.5%                         |
+------------+---------+----------+-------------+------------------------------+

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

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 23:31 UTC|newest]

Thread overview: 95+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-17 23:31 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-12-19  1:37 dpdklab
2024-12-19  0:16 dpdklab
2024-12-19  0:16 dpdklab
2024-12-19  0:16 dpdklab
2024-12-18  8:54 dpdklab
2024-12-18  8:45 dpdklab
2024-12-18  3:56 dpdklab
2024-12-18  3:50 dpdklab
2024-12-18  3:08 dpdklab
2024-12-18  2:56 dpdklab
2024-12-18  0:48 dpdklab
2024-12-18  0:44 dpdklab
2024-12-18  0:26 dpdklab
2024-12-18  0:25 dpdklab
2024-12-18  0:02 dpdklab
2024-12-17 23:33 dpdklab
2024-12-17 23:30 dpdklab
2024-12-17 22:54 dpdklab
2024-12-17 22:39 dpdklab
2024-12-17 22:38 dpdklab
2024-12-04 10:37 dpdklab
2024-12-04 10:06 dpdklab
2024-12-04  9:21 dpdklab
2024-12-04  8:37 dpdklab
2024-12-04  8:26 dpdklab
2024-12-04  8:10 dpdklab
2024-12-04  8:00 dpdklab
2024-12-04  7:55 dpdklab
2024-12-04  6:30 dpdklab
2024-12-04  5:54 dpdklab
2024-12-04  5:36 dpdklab
2024-12-04  5:34 dpdklab
2024-12-04  5:25 dpdklab
2024-12-04  5:06 dpdklab
2024-12-04  4:40 dpdklab
2024-12-04  3:52 dpdklab
2024-12-04  3:20 dpdklab
2024-12-04  3:10 dpdklab
2024-12-04  3:00 dpdklab
2024-12-04  2:59 dpdklab
2024-12-04  2:49 dpdklab
2024-12-04  2:07 dpdklab
2024-12-04  2:03 dpdklab
2024-12-04  2:03 dpdklab
2024-12-04  1:28 dpdklab
2024-12-04  0:55 dpdklab
2024-12-04  0:39 dpdklab
2024-12-04  0:14 dpdklab
2024-12-04  0:01 dpdklab
2024-12-03 23:46 dpdklab
2024-12-03 23:35 dpdklab
2024-12-03 23:31 dpdklab
2024-12-03 23:25 dpdklab
2024-12-03 23:23 dpdklab
2024-12-03 22:57 dpdklab
2024-12-03 22:42 dpdklab
2024-12-03 22:42 dpdklab
2024-12-03 22:06 dpdklab
2024-12-03 22:03 dpdklab
2024-12-03 21:57 dpdklab
2024-12-03 21:54 dpdklab
2024-12-03 21:08 dpdklab
2024-12-03 21:08 dpdklab
2024-12-03 21:06 dpdklab
2024-12-03 20:43 dpdklab
2024-12-03 20:21 dpdklab
2024-12-03 20:14 dpdklab
2024-12-03 18:57 dpdklab
2024-12-02  5:25 dpdklab
2024-12-02  2:10 dpdklab
2024-12-02  2:10 dpdklab
2024-12-02  2:09 dpdklab
2024-12-02  2:04 dpdklab
2024-12-02  1:58 dpdklab
2024-12-02  1:49 dpdklab
2024-12-02  1:46 dpdklab
2024-12-02  1:40 dpdklab
2024-12-02  1:38 dpdklab
2024-12-02  1:25 dpdklab
2024-12-02  1:23 dpdklab
2024-12-01 20:50 dpdklab
2024-12-01 18:46 dpdklab
2024-12-01 18:41 dpdklab
2024-12-01 18:29 dpdklab
2024-12-01 18:29 dpdklab
2024-12-01 18:19 dpdklab
2024-12-01 18:18 dpdklab
2024-12-01 18:11 dpdklab
2024-12-01 18:09 dpdklab
2024-12-01 18:06 dpdklab
2024-12-01 18:01 dpdklab
2024-12-01 17:58 dpdklab
2024-12-01 17:55 dpdklab
2024-12-01 17:51 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=676209b5.050a0220.1f8fec.84b6SMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=jerinj@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).