From: dpdklab@iol.unh.edu
To: Ali Alnubani <alialnu@nvidia.com>, Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@dpdk.org,
David Marchand <david.marchand@redhat.com>,
Thomas Monjalon <thomas@monjalon.net>
Subject: |SUCCESS| pw125191-125192 [PATCH] [2/2] app/testpmd: add testpmd based sleeping
Date: Thu, 16 Mar 2023 16:41:10 +0000 (UTC) [thread overview]
Message-ID: <20230316164110.BE46F6011D@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
Test-Label: iol-mellanox-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/125192
_Performance Testing PASS_
Submitter: Anthony Harivel <aharivel@redhat.com>
Date: Thursday, March 16 2023 15:14:38
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:8c9bfcb1553d756eb5392a56ac7813b3865c3ec7
125191-125192 --> performance testing pass
Test environment and result as below:
Ubuntu 20.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 | num_cpus | num_threads | throughput difference from |
| | | | | expected |
+============+=========+==========+=============+==============================+
| 64 | 256 | 1 | 1 | 0.4% |
+------------+---------+----------+-------------+------------------------------+
| 128 | 256 | 1 | 1 | 0.1% |
+------------+---------+----------+-------------+------------------------------+
| 1024 | 256 | 1 | 1 | 0.1% |
+------------+---------+----------+-------------+------------------------------+
| 256 | 256 | 1 | 1 | 0.2% |
+------------+---------+----------+-------------+------------------------------+
| 1518 | 256 | 1 | 1 | -0.2% |
+------------+---------+----------+-------------+------------------------------+
| 512 | 256 | 1 | 1 | 0.5% |
+------------+---------+----------+-------------+------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/25765/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-03-16 16:41 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-16 16:41 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-03-20 18:40 dpdklab
2023-03-18 19:28 dpdklab
2023-03-18 18:47 dpdklab
2023-03-18 17:38 dpdklab
2023-03-18 17:31 dpdklab
2023-03-17 17:21 dpdklab
2023-03-16 20:19 dpdklab
2023-03-16 19:47 dpdklab
2023-03-16 19:40 dpdklab
2023-03-16 19:14 dpdklab
2023-03-16 19:06 dpdklab
2023-03-16 19:02 dpdklab
2023-03-16 18:41 dpdklab
2023-03-16 18:29 dpdklab
2023-03-16 18:17 dpdklab
2023-03-16 18:05 dpdklab
2023-03-16 17:47 dpdklab
2023-03-16 17:35 dpdklab
2023-03-16 17:33 dpdklab
2023-03-16 17:28 dpdklab
2023-03-16 17:23 dpdklab
2023-03-16 17:09 dpdklab
2023-03-16 17:08 dpdklab
2023-03-16 17:03 dpdklab
2023-03-16 17:02 dpdklab
2023-03-16 16:59 dpdklab
2023-03-16 16:58 dpdklab
2023-03-16 16:56 dpdklab
2023-03-16 16:54 dpdklab
2023-03-16 16:50 dpdklab
2023-03-16 16:48 dpdklab
2023-03-16 16:42 dpdklab
2023-03-16 16:35 dpdklab
2023-03-16 16:27 dpdklab
[not found] <20230316151438.186241-2-aharivel@redhat.com>
2023-03-16 15:04 ` |SUCCESS| pw125191-125192 [PATCH 2/2] " qemudev
2023-03-16 15:08 ` qemudev
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=20230316164110.BE46F6011D@dpdk-ubuntu.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=alialnu@nvidia.com \
--cc=david.marchand@redhat.com \
--cc=dpdk-test-reports@dpdk.org \
--cc=test-report@dpdk.org \
--cc=thomas@monjalon.net \
/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).