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| pw96296 [PATCH] [v3] doc: spell check
Date: Fri, 30 Jul 2021 00:04:55 -0400 (EDT)	[thread overview]
Message-ID: <20210730040455.A44E088E71@noxus.dpdklab.iol.unh.edu> (raw)

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

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

_Performance Testing PASS_

Submitter: Henry Nadeau <hnadeau@iol.unh.edu>
Date: Monday, July 26 2021 16:37:11 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:02e077f35dbc9821dfcb32714ad1096a3ee58d08

96296 --> performance testing pass

Test environment and result as below:

Ubuntu 20.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/5

Detail performance results: 
+------------+---------+----------+-------------+------------------------------+
| frame_size | txd/rxd | num_cpus | num_threads |  throughput difference from  |
|            |         |          |             |           expected           |
+============+=========+==========+=============+==============================+
| 64         | 256     | 1        | 1           | -0.3%                        |
+------------+---------+----------+-------------+------------------------------+
| 1          | 1       | 256      | 128         | -0.1%                        |
+------------+---------+----------+-------------+------------------------------+
| 1          | 1       | 256      | 256         | 0.3%                         |
+------------+---------+----------+-------------+------------------------------+
| 1          | 1       | 256      | 1518        | -0.1%                        |
+------------+---------+----------+-------------+------------------------------+
| 1          | 1       | 256      | 1024        | -0.1%                        |
+------------+---------+----------+-------------+------------------------------+

Ubuntu 20.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/5

Detail performance results: 
+------------+---------+----------+-------------+------------------------------+
| frame_size | txd/rxd | num_cpus | num_threads |  throughput difference from  |
|            |         |          |             |           expected           |
+============+=========+==========+=============+==============================+
| 64         | 256     | 1        | 1           | -0.7%                        |
+------------+---------+----------+-------------+------------------------------+
| 1          | 1       | 256      | 128         | -0.2%                        |
+------------+---------+----------+-------------+------------------------------+
| 1          | 1       | 256      | 256         | -0.0%                        |
+------------+---------+----------+-------------+------------------------------+
| 1          | 1       | 256      | 1518        | 0.2%                         |
+------------+---------+----------+-------------+------------------------------+
| 1          | 1       | 256      | 1024        | -0.1%                        |
+------------+---------+----------+-------------+------------------------------+

Ubuntu 20.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/5

Detail performance results: 
+------------+---------+----------+-------------+------------------------------+
| frame_size | txd/rxd | num_cpus | num_threads |  throughput difference from  |
|            |         |          |             |           expected           |
+============+=========+==========+=============+==============================+
| 64         | 256     | 1        | 1           | -0.4%                        |
+------------+---------+----------+-------------+------------------------------+
| 1          | 1       | 256      | 128         | 0.1%                         |
+------------+---------+----------+-------------+------------------------------+
| 1          | 1       | 256      | 256         | 0.1%                         |
+------------+---------+----------+-------------+------------------------------+
| 1          | 1       | 256      | 1518        | -0.1%                        |
+------------+---------+----------+-------------+------------------------------+
| 1          | 1       | 256      | 1024        | -0.1%                        |
+------------+---------+----------+-------------+------------------------------+

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2021-07-30  4:04 UTC|newest]

Thread overview: 110+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-30  4:04 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-08-10 23:10 dpdklab
2021-08-10 23:05 dpdklab
2021-08-10 22:49 dpdklab
2021-08-10 22:43 dpdklab
2021-08-10 22:28 dpdklab
2021-08-10 22:22 dpdklab
2021-08-10 21:45 dpdklab
2021-08-10 21:40 dpdklab
2021-08-10 21:23 dpdklab
2021-08-10 21:14 dpdklab
2021-08-10 19:34 dpdklab
2021-08-10 19:28 dpdklab
2021-08-10 19:13 dpdklab
2021-08-10 19:07 dpdklab
2021-08-10 18:51 dpdklab
2021-08-10 18:46 dpdklab
2021-07-30  5:37 dpdklab
2021-07-30  5:23 dpdklab
2021-07-30  5:08 dpdklab
2021-07-30  4:51 dpdklab
2021-07-30  4:34 dpdklab
2021-07-30  4:20 dpdklab
2021-07-30  3:49 dpdklab
2021-07-30  3:32 dpdklab
2021-07-30  2:29 dpdklab
2021-07-30  2:12 dpdklab
2021-07-30  1:56 dpdklab
2021-07-30  1:40 dpdklab
2021-07-30  1:25 dpdklab
2021-07-30  1:09 dpdklab
2021-07-29 22:33 dpdklab
2021-07-29 22:16 dpdklab
2021-07-29 22:01 dpdklab
2021-07-29 21:45 dpdklab
2021-07-29 21:29 dpdklab
2021-07-29 21:13 dpdklab
2021-07-29 20:58 dpdklab
2021-07-29 20:41 dpdklab
2021-07-29 20:22 dpdklab
2021-07-29 13:56 dpdklab
2021-07-29 12:50 dpdklab
2021-07-29  9:17 dpdklab
2021-07-29  8:44 dpdklab
2021-07-29  7:17 dpdklab
2021-07-29  6:03 dpdklab
2021-07-29  5:02 dpdklab
2021-07-29  3:12 dpdklab
2021-07-29  1:45 dpdklab
2021-07-29  0:11 dpdklab
2021-07-28 22:50 dpdklab
2021-07-28 20:22 dpdklab
2021-07-28 20:02 dpdklab
2021-07-28 19:54 dpdklab
2021-07-28 19:35 dpdklab
2021-07-28 19:24 dpdklab
2021-07-28 19:02 dpdklab
2021-07-28 18:56 dpdklab
2021-07-28 18:39 dpdklab
2021-07-28 16:37 dpdklab
2021-07-28 16:28 dpdklab
2021-07-28 14:49 dpdklab
2021-07-28 14:29 dpdklab
2021-07-28 14:28 dpdklab
2021-07-28 13:19 dpdklab
2021-07-28 13:02 dpdklab
2021-07-28 12:20 dpdklab
2021-07-28 11:45 dpdklab
2021-07-28 11:27 dpdklab
2021-07-28 10:13 dpdklab
2021-07-28  8:49 dpdklab
2021-07-28  7:57 dpdklab
2021-07-28  6:54 dpdklab
2021-07-28  6:39 dpdklab
2021-07-28  5:53 dpdklab
2021-07-28  5:37 dpdklab
2021-07-28  4:48 dpdklab
2021-07-28  4:11 dpdklab
2021-07-28  3:00 dpdklab
2021-07-28  1:56 dpdklab
2021-07-27 23:30 dpdklab
2021-07-27 23:17 dpdklab
2021-07-27 23:17 dpdklab
2021-07-27 22:59 dpdklab
2021-07-27 22:51 dpdklab
2021-07-27 22:38 dpdklab
2021-07-27 22:34 dpdklab
2021-07-27 22:25 dpdklab
2021-07-27 22:20 dpdklab
2021-07-27 22:18 dpdklab
2021-07-27 21:57 dpdklab
2021-07-27 21:47 dpdklab
2021-07-27 21:37 dpdklab
2021-07-27 21:11 dpdklab
2021-07-27 20:59 dpdklab
2021-07-27 20:51 dpdklab
2021-07-27 20:28 dpdklab
2021-07-27 20:07 dpdklab
2021-07-27 19:57 dpdklab
2021-07-27 19:34 dpdklab
2021-07-27 19:04 dpdklab
2021-07-27 18:47 dpdklab
2021-07-27 18:40 dpdklab
2021-07-27 18:21 dpdklab
2021-07-27 16:32 dpdklab
2021-07-27 16:13 dpdklab
2021-07-27 16:05 dpdklab
2021-07-27 15:44 dpdklab
2021-07-27 15:34 dpdklab
2021-07-27 15:11 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=20210730040455.A44E088E71@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).