automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw137234-137237 [PATCH] [v3,4/4] common/qat: add gen5 devi
Date: Mon, 26 Feb 2024 09:55:50 -0800 (PST)	[thread overview]
Message-ID: <65dcd0a6.050a0220.c2c23.4bf8SMTPIN_ADDED_MISSING@mx.google.com> (raw)

Test-Label: iol-intel-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/137237

_Performance Testing PASS_

Submitter: Ciara Power <ciara.power@intel.com>
Date: Monday, February 26 2024 17:08:18 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:92c0ad70caf3ed6f4b93de6ddaf7bc369737c049

137234-137237 --> performance testing pass

Test environment and result as below:

Ubuntu 20.04
Kernel: 4.15.0-generic
Compiler: gcc 7.4
NIC: Intel Corporation Ethernet Converged Network Adapter 82599ES 10000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/6

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

Ubuntu 20.04
Kernel: 4.15.0-generic
Compiler: gcc 7.4
NIC: Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/4

Detail performance results: 
+----------+-------------+---------+------------+------------------------------+
| num_cpus | num_threads | txd/rxd | frame_size |  throughput difference from  |
|          |             |         |            |           expected           |
+==========+=============+=========+============+==============================+
| 1        | 2           | 512     | 64         | -0.2%                        |
+----------+-------------+---------+------------+------------------------------+
| 1        | 2           | 2048    | 64         | 0.0%                         |
+----------+-------------+---------+------------+------------------------------+
| 1        | 1           | 512     | 64         | -5.2%                        |
+----------+-------------+---------+------------+------------------------------+
| 1        | 1           | 2048    | 64         | -0.1%                        |
+----------+-------------+---------+------------+------------------------------+

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-02-26 17:56 UTC|newest]

Thread overview: 72+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-26 17:55 dpdklab [this message]
     [not found] <20240226170818.533793-5-ciara.power@intel.com>
2024-02-28  2:33 ` dpdklab
2024-02-28  2:36 ` dpdklab
2024-02-28  2:38 ` dpdklab
2024-02-28  2:41 ` dpdklab
  -- strict thread matches above, loose matches on Subject: below --
2024-02-26 23:08 dpdklab
2024-02-26 23:00 dpdklab
2024-02-26 20:54 dpdklab
2024-02-26 20:25 dpdklab
2024-02-26 20:10 dpdklab
2024-02-26 19:34 dpdklab
2024-02-26 18:32 dpdklab
2024-02-26 18:32 dpdklab
2024-02-26 18:30 dpdklab
2024-02-26 18:24 dpdklab
2024-02-26 18:24 dpdklab
2024-02-26 18:23 dpdklab
2024-02-26 18:18 dpdklab
2024-02-26 18:10 dpdklab
2024-02-26 18:05 dpdklab
2024-02-26 18:04 dpdklab
2024-02-26 18:04 dpdklab
2024-02-26 18:04 dpdklab
2024-02-26 18:04 dpdklab
2024-02-26 18:03 dpdklab
2024-02-26 18:03 dpdklab
2024-02-26 18:02 dpdklab
2024-02-26 18:02 dpdklab
2024-02-26 18:02 dpdklab
2024-02-26 18:02 dpdklab
2024-02-26 18:01 dpdklab
2024-02-26 18:01 dpdklab
2024-02-26 18:01 dpdklab
2024-02-26 18:01 dpdklab
2024-02-26 18:01 dpdklab
2024-02-26 18:00 dpdklab
2024-02-26 18:00 dpdklab
2024-02-26 17:59 dpdklab
2024-02-26 17:59 dpdklab
2024-02-26 17:58 dpdklab
2024-02-26 17:58 dpdklab
2024-02-26 17:57 dpdklab
2024-02-26 17:57 dpdklab
2024-02-26 17:56 dpdklab
2024-02-26 17:56 dpdklab
2024-02-26 17:56 dpdklab
2024-02-26 17:56 dpdklab
2024-02-26 17:55 dpdklab
2024-02-26 17:55 dpdklab
2024-02-26 17:55 dpdklab
2024-02-26 17:55 dpdklab
2024-02-26 17:55 dpdklab
2024-02-26 17:54 dpdklab
2024-02-26 17:54 dpdklab
2024-02-26 17:54 dpdklab
2024-02-26 17:54 dpdklab
2024-02-26 17:53 dpdklab
2024-02-26 17:53 dpdklab
2024-02-26 17:53 dpdklab
2024-02-26 17:53 dpdklab
2024-02-26 17:52 dpdklab
2024-02-26 17:52 dpdklab
2024-02-26 17:52 dpdklab
2024-02-26 17:51 dpdklab
2024-02-26 17:51 dpdklab
2024-02-26 17:51 dpdklab
2024-02-26 17:51 dpdklab
2024-02-26 17:50 dpdklab
2024-02-26 17:49 dpdklab
2024-02-26 17:49 dpdklab
2024-02-26 17:49 dpdklab
2024-02-26 17:49 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=65dcd0a6.050a0220.c2c23.4bf8SMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --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).