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| pw88430 [PATCH] [v2] pflock: implementation of phase-fair reader writer locks
Date: Wed,  3 Mar 2021 15:02:50 -0500 (EST)	[thread overview]
Message-ID: <20210303200250.B3CE388E63@noxus.dpdklab.iol.unh.edu> (raw)

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

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

_Performance Testing PASS_

Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Wednesday, March 03 2021 18:30:19 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:e79b0efd989a077d0193e7dbf47f966f65d0c9dc

88430 --> 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.52172%                           |
+------------+---------+-------------------------------------+
| 128        | 256     | 0.24919%                            |
+------------+---------+-------------------------------------+
| 256        | 256     | 0.32474%                            |
+------------+---------+-------------------------------------+
| 512        | 256     | -0.27007%                           |
+------------+---------+-------------------------------------+
| 1024       | 256     | -0.04259%                           |
+------------+---------+-------------------------------------+
| 1518       | 256     | -0.15296%                           |
+------------+---------+-------------------------------------+

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.28949%                            |
+------------+---------+-------------------------------------+
| 128        | 256     | 0.37352%                            |
+------------+---------+-------------------------------------+
| 256        | 256     | 1.57686%                            |
+------------+---------+-------------------------------------+
| 512        | 256     | -0.92103%                           |
+------------+---------+-------------------------------------+
| 1024       | 256     | 0.35146%                            |
+------------+---------+-------------------------------------+
| 1518       | 256     | 0.07402%                            |
+------------+---------+-------------------------------------+

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     | -3.05631%                           |
+------------+---------+-------------------------------------+
| 64         | 256     | -3.49979%                           |
+------------+---------+-------------------------------------+
| 64         | 512     | -3.39393%                           |
+------------+---------+-------------------------------------+
| 64         | 2048    | -3.50365%                           |
+------------+---------+-------------------------------------+

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.27971%                           |
+------------+---------+-------------------------------------+
| 128        | 256     | 0.47173%                            |
+------------+---------+-------------------------------------+
| 256        | 256     | 0.21577%                            |
+------------+---------+-------------------------------------+
| 512        | 256     | -0.12789%                           |
+------------+---------+-------------------------------------+
| 1024       | 256     | -0.01044%                           |
+------------+---------+-------------------------------------+
| 1518       | 256     | 0.01538%                            |
+------------+---------+-------------------------------------+

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2021-03-03 20:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-03 20:02 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-03-04  1:50 dpdklab
2021-03-04  1:49 dpdklab
2021-03-03 20:13 dpdklab
2021-03-03 20:00 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=20210303200250.B3CE388E63@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).