From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu,
David Marchand <david.marchand@redhat.com>,
Thomas Monjalon <thomas@monjalon.net>
Subject: |SUCCESS| pw124738-124753 [PATCH] [v3, 17/17] test/bbdev: remove iter count from bler test
Date: Fri, 3 Mar 2023 05:22:07 +0000 (UTC) [thread overview]
Message-ID: <20230303052207.C37B4601B4@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
Test-Label: iol-broadcom-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/124753
_Performance Testing PASS_
Submitter: Hernan Vargas <hernan.vargas@intel.com>
Date: Thursday, March 02 2023 20:22:11
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:4ef69b2877a24ddb89afaf4bb6f4e73bb52a605b
124738-124753 --> performance testing pass
Test environment and result as below:
Ubuntu 22.04
Kernel: 5.15.0-39-generic
Compiler: gcc gcc (Ubuntu 11.2.0-19ubuntu1) 11.2.0
NIC: Broadcom Inc. and subsidiaries BCM57414 NetXtreme-E 10Gb/25Gb RDMA Ethernet Controller 16d7 25 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/3
Detail performance results:
+------------+---------+----------+-------------+------------------------------+
| frame_size | txd/rxd | num_cpus | num_threads | throughput difference from |
| | | | | expected |
+============+=========+==========+=============+==============================+
| 64 | 128 | 1 | 1 | -1.1% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 512 | 1 | 1 | 0.1% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 2048 | 1 | 1 | -3.1% |
+------------+---------+----------+-------------+------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/25599/
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-03 5:22 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-03 5:22 dpdklab [this message]
[not found] <20230302202211.170017-18-hernan.vargas@intel.com>
2023-03-06 7:15 ` |SUCCESS| pw124738-124753 [PATCH v3 " qemudev
2023-03-06 7:15 ` qemudev
-- strict thread matches above, loose matches on Subject: below --
2023-03-04 19:55 |SUCCESS| pw124738-124753 [PATCH] [v3, " dpdklab
2023-03-04 19:52 dpdklab
2023-03-04 19:39 dpdklab
2023-03-04 19:39 dpdklab
2023-03-04 19:31 dpdklab
2023-03-04 19:30 dpdklab
2023-03-04 19:29 dpdklab
2023-03-04 19:28 dpdklab
2023-03-04 19:26 dpdklab
2023-03-04 19:24 dpdklab
2023-03-04 19:20 dpdklab
2023-03-04 19:17 dpdklab
2023-03-04 19:16 dpdklab
2023-03-04 19:16 dpdklab
2023-03-04 19:15 dpdklab
2023-03-04 19:14 dpdklab
2023-03-04 19:10 dpdklab
2023-03-04 19:04 dpdklab
2023-03-04 19:01 dpdklab
2023-03-04 18:55 dpdklab
2023-03-04 18:53 dpdklab
2023-03-04 18:43 dpdklab
2023-03-04 18:41 dpdklab
2023-03-04 18:40 dpdklab
2023-03-04 18:38 dpdklab
2023-03-04 18:26 dpdklab
2023-03-03 19:59 dpdklab
2023-03-03 17:55 dpdklab
2023-03-03 10:53 dpdklab
2023-03-03 9:24 dpdklab
2023-03-03 8:29 dpdklab
2023-03-03 7:23 dpdklab
2023-03-03 6:19 dpdklab
2023-03-03 5:43 dpdklab
2023-03-03 5:38 dpdklab
2023-03-03 5:30 dpdklab
2023-03-03 5:30 dpdklab
2023-03-03 5:28 dpdklab
2023-03-03 5:28 dpdklab
2023-03-03 5:24 dpdklab
2023-03-03 5:24 dpdklab
2023-03-03 5:22 dpdklab
2023-03-03 5:21 dpdklab
2023-03-03 5:19 dpdklab
2023-03-03 5:12 dpdklab
2023-03-03 5:06 dpdklab
2023-03-03 5:03 dpdklab
2023-03-03 4:54 dpdklab
2023-03-03 4:54 dpdklab
2023-03-03 4:54 dpdklab
2023-03-03 4:50 dpdklab
2023-03-03 4:48 dpdklab
2023-03-03 4:47 dpdklab
2023-03-03 4:47 dpdklab
2023-03-03 4:46 dpdklab
2023-03-03 4:42 dpdklab
2023-03-03 4:37 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=20230303052207.C37B4601B4@dpdk-ubuntu.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=david.marchand@redhat.com \
--cc=dpdk-test-reports@iol.unh.edu \
--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).