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: |SUCCESS| pw128425-128440 [PATCH] [v11,16/16] examples/l3fwd-graph:
Date: Thu, 08 Jun 2023 09:34:13 -0700 (PDT)	[thread overview]
Message-ID: <64820305.810a0220.495cc.0490SMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Performance Testing PASS_

Submitter: Zhirun Yan <zhirun.yan@intel.com>
Date: Thursday, June 08 2023 15:18:44 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:55ead98d1de1b02fa563e822a67c7adc0361ddfb

128425-128440 --> performance testing pass

Test environment and result as below:

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

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

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-06-08 16:34 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-08 16:34 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-06-17  0:13 dpdklab
2023-06-17  0:12 dpdklab
2023-06-09 21:10 dpdklab
2023-06-09 18:33 dpdklab
2023-06-09  2:29 dpdklab
2023-06-09  2:12 dpdklab
2023-06-09  2:09 dpdklab
2023-06-09  1:58 dpdklab
2023-06-09  1:54 dpdklab
2023-06-08 22:39 dpdklab
2023-06-08 22:36 dpdklab
2023-06-08 20:03 dpdklab
2023-06-08 17:39 dpdklab
2023-06-08 17:20 dpdklab
2023-06-08 16:49 dpdklab
2023-06-08 16:41 dpdklab
2023-06-08 16:41 dpdklab
2023-06-08 16:37 dpdklab
2023-06-08 16:25 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=64820305.810a0220.495cc.0490SMTPIN_ADDED_MISSING@mx.google.com \
    --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).