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| pw82237 [PATCH] examples/pipeline: fix resource leak
Date: Tue, 27 Oct 2020 17:00:56 -0400 (EDT)	[thread overview]
Message-ID: <20201027210056.EC361A76A@noxus.dpdklab.iol.unh.edu> (raw)

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

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

_Performance Testing PASS_

Submitter: Dumitrescu, Cristian <cristian.dumitrescu@intel.com>
Date: Monday, October 26 2020 21:23:55 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:5d7366372888ba654d3ba02b2b06de469ec433b9

82237 --> 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.250                              |
+------------+---------+-------------------------------------+
| 128        | 256     | -0.183                              |
+------------+---------+-------------------------------------+
| 256        | 256     | -0.095                              |
+------------+---------+-------------------------------------+
| 512        | 256     | -0.068                              |
+------------+---------+-------------------------------------+
| 1024       | 256     | -0.119                              |
+------------+---------+-------------------------------------+
| 1518       | 256     | -0.016                              |
+------------+---------+-------------------------------------+

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.068                               |
+------------+---------+-------------------------------------+
| 128        | 256     | 0.108                               |
+------------+---------+-------------------------------------+
| 256        | 256     | 0.032                               |
+------------+---------+-------------------------------------+
| 512        | 256     | -0.060                              |
+------------+---------+-------------------------------------+
| 1024       | 256     | 0.013                               |
+------------+---------+-------------------------------------+
| 1518       | 256     | 0.003                               |
+------------+---------+-------------------------------------+

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.082                               |
+------------+---------+-------------------------------------+
| 128        | 256     | 0.037                               |
+------------+---------+-------------------------------------+
| 256        | 256     | 0.183                               |
+------------+---------+-------------------------------------+
| 512        | 256     | -0.046                              |
+------------+---------+-------------------------------------+
| 1024       | 256     | -0.037                              |
+------------+---------+-------------------------------------+
| 1518       | 256     | -0.013                              |
+------------+---------+-------------------------------------+

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2020-10-27 21:01 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-27 21:00 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-10-27 20:09 dpdklab
2020-10-27 14:23 dpdklab
2020-10-27 13:57 dpdklab
2020-10-27 13:32 dpdklab
2020-10-27 13:25 dpdklab
2020-10-27 13:09 dpdklab
2020-10-27 13:07 dpdklab
2020-10-27 12:14 dpdklab
2020-10-27 12:05 dpdklab
2020-10-27 11:59 dpdklab
2020-10-27 11:51 dpdklab
     [not found] <20201026212355.8769-1-cristian.dumitrescu@intel.com>
2020-10-26 21:25 ` checkpatch

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=20201027210056.EC361A76A@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).