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, Akhil Goyal <gakhil@marvell.com>
Subject: |SUCCESS| [GIT MASTER] 34325c1a5d1140ac702d3a5d804f86aebe462589
Date: Tue, 10 Oct 2023 09:58:13 -0700 (PDT)	[thread overview]
Message-ID: <652582a5.020a0220.cd34e.ad30SMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Performance Testing PASS_

Branch: dpdk-next-crypto

34325c1a5d1140ac702d3a5d804f86aebe462589 --> 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.1%                        |
+------------+---------+----------+-------------+------------------------------+
| 128        | 256     | 1        | 1           | 0.0%                         |
+------------+---------+----------+-------------+------------------------------+
| 1024       | 256     | 1        | 1           | 0.3%                         |
+------------+---------+----------+-------------+------------------------------+
| 256        | 256     | 1        | 1           | -0.2%                        |
+------------+---------+----------+-------------+------------------------------+
| 1518       | 256     | 1        | 1           | 0.2%                         |
+------------+---------+----------+-------------+------------------------------+
| 512        | 256     | 1        | 1           | -0.1%                        |
+------------+---------+----------+-------------+------------------------------+

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-10-10 16:58 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-10 16:58 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-10-12 12:09 dpdklab
2023-10-11 23:36 dpdklab
2023-10-11 23:31 dpdklab
2023-10-11 23:26 dpdklab
2023-10-11 20:05 dpdklab
2023-10-10 23:36 dpdklab
2023-10-10 22:04 dpdklab
2023-10-10 22:01 dpdklab
2023-10-10 22:00 dpdklab
2023-10-10 21:59 dpdklab
2023-10-10 21:23 dpdklab
2023-10-10 21:23 dpdklab
2023-10-10 21:19 dpdklab
2023-10-10 21:09 dpdklab
2023-10-10 21:08 dpdklab
2023-10-10 21:03 dpdklab
2023-10-10 21:03 dpdklab
2023-10-10 21:03 dpdklab
2023-10-10 21:03 dpdklab
2023-10-10 21:03 dpdklab
2023-10-10 21:03 dpdklab
2023-10-10 21:03 dpdklab
2023-10-10 21:00 dpdklab
2023-10-10 20:59 dpdklab
2023-10-10 20:59 dpdklab
2023-10-10 20:58 dpdklab
2023-10-10 20:58 dpdklab
2023-10-10 20:57 dpdklab
2023-10-10 20:57 dpdklab
2023-10-10 20:57 dpdklab
2023-10-10 20:56 dpdklab
2023-10-10 20:56 dpdklab
2023-10-10 20:56 dpdklab
2023-10-10 20:56 dpdklab
2023-10-10 20:55 dpdklab
2023-10-10 20:55 dpdklab
2023-10-10 20:54 dpdklab
2023-10-10 20:53 dpdklab
2023-10-10 20:52 dpdklab
2023-10-10 20:51 dpdklab
2023-10-10 20:48 dpdklab
2023-10-10 20:29 dpdklab
2023-10-10 18:45 dpdklab
2023-10-10 18:43 dpdklab
2023-10-10 18:32 dpdklab
2023-10-10 17:58 dpdklab
2023-10-10 17:00 dpdklab
2023-10-10 16:55 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=652582a5.020a0220.cd34e.ad30SMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=alialnu@nvidia.com \
    --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).