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@dpdk.org
Subject: [dpdk-test-report] |SUCCESS| pw88219 [PATCH] app/eventdev: fix timeout accuracy
Date: Thu, 25 Feb 2021 08:48:31 -0500 (EST)	[thread overview]
Message-ID: <20210225134831.578D41F18F@noxus.dpdklab.iol.unh.edu> (raw)

[-- Attachment #1: Type: text/plain, Size: 4861 bytes --]

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

_Performance Testing PASS_

Submitter: Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>
Date: Thursday, February 25 2021 12:01:43 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:51fe32138c860992f228dbf19416ffd3b8e8baf4

88219 --> performance testing pass

Test environment and result as below:

Ubuntu 18.04
Kernel: 4.15.0-generic
Compiler: gcc 7.4
NIC: Mellanox ConnectX-5 100000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/6

Detail performance results: 
+------------+---------+-------------------------------------+
| frame_size | txd/rxd | throughput difference from expected |
+============+=========+=====================================+
| 64         | 256     | -0.29123%                           |
+------------+---------+-------------------------------------+
| 128        | 256     | 0.05166%                            |
+------------+---------+-------------------------------------+
| 256        | 256     | -0.18689%                           |
+------------+---------+-------------------------------------+
| 512        | 256     | 0.60852%                            |
+------------+---------+-------------------------------------+
| 1024       | 256     | 1.13936%                            |
+------------+---------+-------------------------------------+
| 1518       | 256     | -0.07061%                           |
+------------+---------+-------------------------------------+

Ubuntu 18.04
Kernel: 4.15.0-generic
Compiler: gcc 7.4
NIC: Mellanox ConnectX-4 Lx 25000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/6

Detail performance results: 
+------------+---------+-------------------------------------+
| frame_size | txd/rxd | throughput difference from expected |
+============+=========+=====================================+
| 64         | 256     | -0.72781%                           |
+------------+---------+-------------------------------------+
| 128        | 256     | 0.13829%                            |
+------------+---------+-------------------------------------+
| 256        | 256     | -1.091%                             |
+------------+---------+-------------------------------------+
| 512        | 256     | 0.09419%                            |
+------------+---------+-------------------------------------+
| 1024       | 256     | -0.15038%                           |
+------------+---------+-------------------------------------+
| 1518       | 256     | 0.02464%                            |
+------------+---------+-------------------------------------+

Ubuntu 18.04 ARM
Kernel: 4.15.0-132-generic
Compiler: gcc 7.5
NIC: Arm Mellanox ConnectX-5 10000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/4

Detail performance results: 
+------------+---------+-------------------------------------+
| frame_size | txd/rxd | throughput difference from expected |
+============+=========+=====================================+
| 64         | 128     | -2.00963%                           |
+------------+---------+-------------------------------------+
| 64         | 256     | -2.60134%                           |
+------------+---------+-------------------------------------+
| 64         | 512     | -2.11201%                           |
+------------+---------+-------------------------------------+
| 64         | 2048    | -2.44004%                           |
+------------+---------+-------------------------------------+

Ubuntu 18.04
Kernel: 4.15.0-generic
Compiler: gcc 7.4
NIC: Mellanox ConnectX-4 Lx 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/6

Detail performance results: 
+------------+---------+-------------------------------------+
| frame_size | txd/rxd | throughput difference from expected |
+============+=========+=====================================+
| 64         | 256     | 0.06284%                            |
+------------+---------+-------------------------------------+
| 128        | 256     | 0.88615%                            |
+------------+---------+-------------------------------------+
| 256        | 256     | -0.1388%                            |
+------------+---------+-------------------------------------+
| 512        | 256     | 0.19197%                            |
+------------+---------+-------------------------------------+
| 1024       | 256     | -0.10446%                           |
+------------+---------+-------------------------------------+
| 1518       | 256     | -0.18428%                           |
+------------+---------+-------------------------------------+

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2021-02-25 13:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-25 13:48 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-02-25 22:02 dpdklab
2021-02-25 22:02 dpdklab
2021-02-25 14:44 dpdklab
2021-02-25 13:33 dpdklab
2021-02-25 13:22 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=20210225134831.578D41F18F@noxus.dpdklab.iol.unh.edu \
    --to=dpdklab@iol.unh.edu \
    --cc=alialnu@nvidia.com \
    --cc=dpdk-test-reports@dpdk.org \
    --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).