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| pw136008 [PATCH] [v2] lib/telemetry:fix telemetry conns le
Date: Sat, 20 Jan 2024 23:45:09 -0800 (PST)	[thread overview]
Message-ID: <65accb85.050a0220.3e21e.427cSMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Performance Testing PASS_

Submitter: Shaowei Sun <1819846787@qq.com>
Date: Saturday, January 20 2024 08:58:32 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:515e1a4f4cddd33fcb35328a73449d30a8edfaf6

136008 --> 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 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.4%                        |
+----------+-------------+---------+------------+------------------------------+
| 1        | 2           | 2048    | 64         | 1.4%                         |
+----------+-------------+---------+------------+------------------------------+
| 1        | 1           | 512     | 64         | -4.8%                        |
+----------+-------------+---------+------------+------------------------------+
| 1        | 1           | 2048    | 64         | 7.0%                         |
+----------+-------------+---------+------------+------------------------------+

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.1%                        |
+----------+-------------+---------+------------+------------------------------+
| 1        | 2           | 512     | 64         | 0.0%                         |
+----------+-------------+---------+------------+------------------------------+
| 1        | 2           | 2048    | 64         | -0.5%                        |
+----------+-------------+---------+------------+------------------------------+
| 1        | 1           | 128     | 64         | -0.6%                        |
+----------+-------------+---------+------------+------------------------------+
| 1        | 1           | 512     | 64         | 0.1%                         |
+----------+-------------+---------+------------+------------------------------+
| 1        | 1           | 2048    | 64         | 0.0%                         |
+----------+-------------+---------+------------+------------------------------+

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-01-21  7:45 UTC|newest]

Thread overview: 60+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-21  7:45 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-01-22 21:34 dpdklab
2024-01-22 21:27 dpdklab
2024-01-21 11:16 dpdklab
2024-01-21 11:03 dpdklab
2024-01-21 10:42 dpdklab
2024-01-21 10:37 dpdklab
2024-01-21  9:35 dpdklab
2024-01-21  9:23 dpdklab
2024-01-21  9:16 dpdklab
2024-01-21  9:14 dpdklab
2024-01-21  9:14 dpdklab
2024-01-21  9:11 dpdklab
2024-01-21  9:11 dpdklab
2024-01-21  9:06 dpdklab
2024-01-21  9:03 dpdklab
2024-01-21  9:01 dpdklab
2024-01-21  8:56 dpdklab
2024-01-21  8:56 dpdklab
2024-01-21  8:53 dpdklab
2024-01-21  8:52 dpdklab
2024-01-21  8:51 dpdklab
2024-01-21  8:51 dpdklab
2024-01-21  8:48 dpdklab
2024-01-21  8:45 dpdklab
2024-01-21  8:43 dpdklab
2024-01-21  8:43 dpdklab
2024-01-21  8:42 dpdklab
2024-01-21  8:40 dpdklab
2024-01-21  8:39 dpdklab
2024-01-21  8:38 dpdklab
2024-01-21  8:37 dpdklab
2024-01-21  8:36 dpdklab
2024-01-21  8:33 dpdklab
2024-01-21  8:30 dpdklab
2024-01-21  8:17 dpdklab
2024-01-21  8:11 dpdklab
2024-01-21  8:10 dpdklab
2024-01-21  8:08 dpdklab
2024-01-21  8:08 dpdklab
2024-01-21  8:07 dpdklab
2024-01-21  8:06 dpdklab
2024-01-21  8:06 dpdklab
2024-01-21  8:04 dpdklab
2024-01-21  8:04 dpdklab
2024-01-21  8:02 dpdklab
2024-01-21  8:02 dpdklab
2024-01-21  8:00 dpdklab
2024-01-21  7:59 dpdklab
2024-01-21  7:57 dpdklab
2024-01-21  7:57 dpdklab
2024-01-21  7:56 dpdklab
2024-01-21  7:56 dpdklab
2024-01-21  7:54 dpdklab
2024-01-21  7:45 dpdklab
2024-01-21  7:26 dpdklab
2024-01-21  7:24 dpdklab
2024-01-21  7:21 dpdklab
2024-01-21  7:14 dpdklab
2024-01-21  7:12 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=65accb85.050a0220.3e21e.427cSMTPIN_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).