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
Subject: |SUCCESS| pw130773-130775 [PATCH] [3/3] test/event: add event link p
Date: Fri, 25 Aug 2023 17:29:31 -0700 (PDT)	[thread overview]
Message-ID: <64e9476b.050a0220.cea1c.bbe8SMTPIN_ADDED_MISSING@mx.google.com> (raw)

Test-Label: iol-mellanox-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/130775

_Performance Testing PASS_

Submitter: Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>
Date: Friday, August 25 2023 18:44:35 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:934c0ccbfe881d861d749a9f8fb146d5f134c04c

130773-130775 --> 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.3%                        |
+------------+---------+----------+-------------+------------------------------+
| 128        | 256     | 1        | 1           | -0.0%                        |
+------------+---------+----------+-------------+------------------------------+
| 1024       | 256     | 1        | 1           | -0.1%                        |
+------------+---------+----------+-------------+------------------------------+
| 256        | 256     | 1        | 1           | -0.1%                        |
+------------+---------+----------+-------------+------------------------------+
| 1518       | 256     | 1        | 1           | 0.1%                         |
+------------+---------+----------+-------------+------------------------------+
| 512        | 256     | 1        | 1           | -0.3%                        |
+------------+---------+----------+-------------+------------------------------+

To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/27451/

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-08-26  0:29 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-26  0:29 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-08-26  2:54 dpdklab
2023-08-26  2:53 dpdklab
2023-08-26  2:53 dpdklab
2023-08-26  2:49 dpdklab
2023-08-26  2:33 dpdklab
2023-08-26  2:32 dpdklab
2023-08-26  2:27 dpdklab
2023-08-26  2:27 dpdklab
2023-08-26  2:23 dpdklab
2023-08-26  2:23 dpdklab
2023-08-26  2:21 dpdklab
2023-08-26  1:45 dpdklab
2023-08-26  1:30 dpdklab
2023-08-26  1:24 dpdklab
2023-08-26  1:21 dpdklab
2023-08-26  1:19 dpdklab
2023-08-26  1:19 dpdklab
2023-08-26  1:18 dpdklab
2023-08-26  1:18 dpdklab
2023-08-26  1:18 dpdklab
2023-08-26  1:17 dpdklab
2023-08-26  1:12 dpdklab
2023-08-26  1:10 dpdklab
2023-08-26  1:10 dpdklab
2023-08-26  1:07 dpdklab
2023-08-26  1:04 dpdklab
2023-08-26  1:03 dpdklab
2023-08-26  0:59 dpdklab
2023-08-26  0:59 dpdklab
2023-08-26  0:58 dpdklab
2023-08-26  0:58 dpdklab
2023-08-26  0:53 dpdklab
2023-08-26  0:53 dpdklab
2023-08-26  0:52 dpdklab
2023-08-26  0:52 dpdklab
2023-08-26  0:52 dpdklab
2023-08-26  0:51 dpdklab
2023-08-26  0:50 dpdklab
2023-08-26  0:49 dpdklab
2023-08-26  0:49 dpdklab
2023-08-26  0:45 dpdklab
2023-08-26  0:44 dpdklab
2023-08-26  0:44 dpdklab
2023-08-26  0:42 dpdklab
2023-08-26  0:41 dpdklab
2023-08-26  0:40 dpdklab
2023-08-26  0:40 dpdklab
2023-08-26  0:35 dpdklab
2023-08-26  0:33 dpdklab
2023-08-26  0:25 dpdklab
2023-08-26  0:21 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=64e9476b.050a0220.cea1c.bbe8SMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=alialnu@nvidia.com \
    --cc=dpdk-test-reports@iol.unh.edu \
    --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).