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: [dpdk-test-report] |SUCCESS| pw87831 [PATCH] devtools: add llx format specifier check
Date: Tue,  9 Feb 2021 16:37:34 -0500 (EST)	[thread overview]
Message-ID: <20210209213734.480BA30560@noxus.dpdklab.iol.unh.edu> (raw)

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

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

_Performance Testing PASS_

Submitter: Ferruh Yigit <ferruh.yigit@intel.com>
Date: Tuesday, February 09 2021 15:26:43 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:a69f94e934ccf9a6a6401e4f272cb2407783c2cb

87831 --> performance testing pass

Test environment and result as below:

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.6901448452144336%                 |
+------------+---------+-------------------------------------+
| 128        | 256     | -1.867702074594714%                 |
+------------+---------+-------------------------------------+
| 256        | 256     | 0.021949078138719005%               |
+------------+---------+-------------------------------------+
| 512        | 256     | -0.010645092612299827%              |
+------------+---------+-------------------------------------+
| 1024       | 256     | 0.09412256850031732%                |
+------------+---------+-------------------------------------+
| 1518       | 256     | 0.06167129201357459%                |
+------------+---------+-------------------------------------+

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.09980039920160734%               |
+------------+---------+-------------------------------------+
| 128        | 256     | 0.027686450943066685%               |
+------------+---------+-------------------------------------+
| 256        | 256     | -0.8967071736573884%                |
+------------+---------+-------------------------------------+
| 512        | 256     | -0.44364815288797543%               |
+------------+---------+-------------------------------------+
| 1024       | 256     | -0.06690081953504678%               |
+------------+---------+-------------------------------------+
| 1518       | 256     | 0.29585798816566977%                |
+------------+---------+-------------------------------------+

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.009629474565629%                 |
+------------+---------+-------------------------------------+
| 64         | 256     | -1.587964897618045%                 |
+------------+---------+-------------------------------------+
| 64         | 512     | -1.691709572344222%                 |
+------------+---------+-------------------------------------+
| 64         | 2048    | -2.9405630865484884%                |
+------------+---------+-------------------------------------+

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.35622915249847137%               |
+------------+---------+-------------------------------------+
| 128        | 256     | 0.09805372604158455%                |
+------------+---------+-------------------------------------+
| 256        | 256     | 0.49343753130949486%                |
+------------+---------+-------------------------------------+
| 512        | 256     | 0.8799858494737687%                 |
+------------+---------+-------------------------------------+
| 1024       | 256     | 1.894865525672376%                  |
+------------+---------+-------------------------------------+
| 1518       | 256     | -0.15279736718382583%               |
+------------+---------+-------------------------------------+

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2021-02-09 21:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-09 21:37 dpdklab [this message]
     [not found] <20210209152643.1832506-1-ferruh.yigit@intel.com>
2021-02-16  9:35 ` checkpatch
  -- strict thread matches above, loose matches on Subject: below --
2021-02-10 15:03 dpdklab
2021-02-09 19:18 dpdklab
2021-02-09 17:28 dpdklab
2021-02-09 17:23 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=20210209213734.480BA30560@noxus.dpdklab.iol.unh.edu \
    --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).