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| pw125844 [PATCH] app/crypto-perf: change buffer size based on optype
Date: Thu, 6 Apr 2023 13:46:48 +0000 (UTC) [thread overview]
Message-ID: <20230406134648.A7F2960092@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
Test-Label: iol-mellanox-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/125844
_Performance Testing PASS_
Submitter: Tejasree Kondoj <ktejasree@marvell.com>
Date: Thursday, April 06 2023 08:16:20
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:c682c8991963be243dcc3b7cdc9d6984a1961f4e
125844 --> 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.1% |
+------------+---------+----------+-------------+------------------------------+
| 128 | 256 | 1 | 1 | 0.3% |
+------------+---------+----------+-------------+------------------------------+
| 1024 | 256 | 1 | 1 | -0.1% |
+------------+---------+----------+-------------+------------------------------+
| 256 | 256 | 1 | 1 | -0.1% |
+------------+---------+----------+-------------+------------------------------+
| 1518 | 256 | 1 | 1 | 0.2% |
+------------+---------+----------+-------------+------------------------------+
| 512 | 256 | 1 | 1 | -0.2% |
+------------+---------+----------+-------------+------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/25934/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-04-06 13:46 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-06 13:46 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-04-07 3:27 dpdklab
2023-04-07 2:57 dpdklab
2023-04-07 1:34 dpdklab
2023-04-06 22:29 dpdklab
2023-04-06 21:56 dpdklab
2023-04-06 21:22 dpdklab
2023-04-06 21:13 dpdklab
2023-04-06 21:10 dpdklab
2023-04-06 21:08 dpdklab
2023-04-06 21:03 dpdklab
2023-04-06 21:01 dpdklab
2023-04-06 20:59 dpdklab
2023-04-06 20:51 dpdklab
2023-04-06 14:05 dpdklab
2023-04-06 14:02 dpdklab
2023-04-06 13:57 dpdklab
2023-04-06 13:56 dpdklab
2023-04-06 13:53 dpdklab
2023-04-06 13:47 dpdklab
2023-04-06 13:45 dpdklab
2023-04-06 13:45 dpdklab
2023-04-06 13:40 dpdklab
2023-04-06 13:39 dpdklab
2023-04-06 13:36 dpdklab
[not found] <20230406081620.497772-1-ktejasree@marvell.com>
2023-04-06 8:07 ` qemudev
2023-04-06 8:11 ` qemudev
2023-04-06 8:17 ` checkpatch
2023-04-06 9:58 ` 0-day Robot
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=20230406134648.A7F2960092@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).