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| pw136006 [PATCH] [v2] lib/telemetry:fix telemetry conns le
Date: Sat, 20 Jan 2024 05:20:50 -0800 (PST) [thread overview]
Message-ID: <65abc8b2.050a0220.3b4d8.4d87SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-mellanox-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/136006
_Performance Testing PASS_
Submitter: Shaowei Sun <1819846787@qq.com>
Date: Saturday, January 20 2024 08:32:18
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:515e1a4f4cddd33fcb35328a73449d30a8edfaf6
136006 --> performance testing pass
Test environment and result as below:
Ubuntu 22.04
Kernel: 5.15.0-78-generic
Compiler: gcc 11.4.0
NIC: Mellanox ConnectX-6 Lx 25000 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.1% |
+------------+---------+----------+-------------+------------------------------+
| 128 | 256 | 1 | 1 | 0.1% |
+------------+---------+----------+-------------+------------------------------+
| 1024 | 256 | 1 | 1 | 0.0% |
+------------+---------+----------+-------------+------------------------------+
| 256 | 256 | 1 | 1 | 0.0% |
+------------+---------+----------+-------------+------------------------------+
| 1518 | 256 | 1 | 1 | -0.1% |
+------------+---------+----------+-------------+------------------------------+
| 512 | 256 | 1 | 1 | 0.2% |
+------------+---------+----------+-------------+------------------------------+
Ubuntu 22.04
Kernel: 5.15.0-78-generic
Compiler: gcc 11.4.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.1% |
+------------+---------+----------+-------------+------------------------------+
| 128 | 256 | 1 | 1 | 0.0% |
+------------+---------+----------+-------------+------------------------------+
| 1024 | 256 | 1 | 1 | 0.0% |
+------------+---------+----------+-------------+------------------------------+
| 256 | 256 | 1 | 1 | -0.2% |
+------------+---------+----------+-------------+------------------------------+
| 1518 | 256 | 1 | 1 | 0.1% |
+------------+---------+----------+-------------+------------------------------+
| 512 | 256 | 1 | 1 | -0.2% |
+------------+---------+----------+-------------+------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/28919/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-01-20 13:20 UTC|newest]
Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-20 13:20 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-01-22 20:15 dpdklab
2024-01-22 20:08 dpdklab
2024-01-20 15:50 dpdklab
2024-01-20 10:43 dpdklab
2024-01-20 10:18 dpdklab
2024-01-20 9:56 dpdklab
2024-01-20 9:55 dpdklab
2024-01-20 9:54 dpdklab
2024-01-20 9:47 dpdklab
2024-01-20 9:46 dpdklab
2024-01-20 9:45 dpdklab
2024-01-20 9:43 dpdklab
2024-01-20 9:43 dpdklab
2024-01-20 9:43 dpdklab
2024-01-20 9:42 dpdklab
2024-01-20 9:41 dpdklab
2024-01-20 9:40 dpdklab
2024-01-20 9:40 dpdklab
2024-01-20 9:39 dpdklab
2024-01-20 9:39 dpdklab
2024-01-20 9:38 dpdklab
2024-01-20 9:38 dpdklab
2024-01-20 9:37 dpdklab
2024-01-20 9:37 dpdklab
2024-01-20 9:37 dpdklab
2024-01-20 9:36 dpdklab
2024-01-20 9:36 dpdklab
2024-01-20 9:36 dpdklab
2024-01-20 9:36 dpdklab
2024-01-20 9:35 dpdklab
2024-01-20 9:35 dpdklab
2024-01-20 9:35 dpdklab
2024-01-20 9:35 dpdklab
2024-01-20 9:35 dpdklab
2024-01-20 9:35 dpdklab
2024-01-20 9:34 dpdklab
2024-01-20 9:34 dpdklab
2024-01-20 9:34 dpdklab
2024-01-20 9:34 dpdklab
2024-01-20 9:34 dpdklab
2024-01-20 9:34 dpdklab
2024-01-20 9:34 dpdklab
2024-01-20 9:33 dpdklab
2024-01-20 9:33 dpdklab
2024-01-20 9:33 dpdklab
2024-01-20 9:33 dpdklab
2024-01-20 9:32 dpdklab
2024-01-20 9:32 dpdklab
2024-01-20 9:32 dpdklab
2024-01-20 9:32 dpdklab
2024-01-20 9:32 dpdklab
2024-01-20 9:31 dpdklab
2024-01-20 9:31 dpdklab
2024-01-20 9:31 dpdklab
2024-01-20 9:31 dpdklab
2024-01-20 9:30 dpdklab
2024-01-20 9:30 dpdklab
2024-01-20 9:29 dpdklab
2024-01-20 9:29 dpdklab
2024-01-20 9:29 dpdklab
2024-01-20 9:29 dpdklab
2024-01-20 9:29 dpdklab
2024-01-20 9:29 dpdklab
2024-01-20 9:28 dpdklab
2024-01-20 9:28 dpdklab
2024-01-20 9:28 dpdklab
2024-01-20 9:27 dpdklab
2024-01-20 9:27 dpdklab
2024-01-20 9:26 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=65abc8b2.050a0220.3b4d8.4d87SMTPIN_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).