From: dpdklab@iol.unh.edu
To: Patrick Robb <probb@iol.unh.edu>, Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu, Morten Brorup <mb@smartsharesystems.com>
Subject: |FAILURE| pw144610 [PATCH] [RFC,v12] mempool: fix mempool cache size
Date: Sat, 28 Sep 2024 14:04:36 -0700 (PDT) [thread overview]
Message-ID: <66f86f64.050a0220.2d6ad7.d035SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240928193841.1993128-1-mb@smartsharesystems.com>
Test-Label: iol-broadcom-Performance
Test-Status: FAILURE
http://dpdk.org/patch/144610
_Performance Testing issues_
Submitter: Morten Brorup <mb@smartsharesystems.com>
Date: Saturday, September 28 2024 19:38:41
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:bf0ff8df59c7e32f95c0b542cc4a7918f8a3da84
144610 --> performance testing issues
Upstream job id: Template-DTS-Pipeline#183885
Test environment and result as below:
Ubuntu 22.04
Kernel: 5.15.0-100-generic
Compiler: gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
NIC: Broadcom Inc. and subsidiaries BCM57414 NetXtreme-E 10Gb/25Gb RDMA Ethernet Controller 16d7 25 Mbps
Fail/Total: 1/3
Failed cases list:
- DTS https://dpdklab.iol.unh.edu/results/testcases/1/
Detail performance results:
+------------+---------+----------+-------------+------------------------------+
| frame_size | txd/rxd | num_cpus | num_threads | throughput difference from |
| | | | | expected |
+============+=========+==========+=============+==============================+
| 64 | 128 | 1 | 1 | -12.7% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 512 | 1 | 1 | 3.0% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 2048 | 1 | 1 | 0.6% |
+------------+---------+----------+-------------+------------------------------+
Ubuntu 22.04 ARM
Kernel: 5.15.83+
Compiler: gcc 11.4.0
NIC: Arm Broadcom Inc. brcm_57414 25000 Mbps
Fail/Total: 0/2
Detail performance results:
+------------+---------+----------+-------------+------------------------------+
| frame_size | txd/rxd | num_cpus | num_threads | throughput difference from |
| | | | | expected |
+============+=========+==========+=============+==============================+
| 64 | 512 | 1 | 1 | -0.5% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 2048 | 1 | 1 | -0.5% |
+------------+---------+----------+-------------+------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/31171/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next prev parent reply other threads:[~2024-09-28 21:04 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240928193841.1993128-1-mb@smartsharesystems.com>
2024-09-28 19:12 ` |SUCCESS| pw144610 [RFC PATCH v12] " qemudev
2024-09-28 19:17 ` qemudev
2024-09-28 19:39 ` checkpatch
2024-09-28 20:16 ` |PENDING| pw144610 [PATCH] [RFC,v12] " dpdklab
2024-09-28 20:19 ` |FAILURE| " dpdklab
2024-09-28 20:23 ` |PENDING| " dpdklab
2024-09-28 20:24 ` dpdklab
2024-09-28 20:26 ` |SUCCESS| " dpdklab
2024-09-28 20:28 ` dpdklab
2024-09-28 20:31 ` dpdklab
2024-09-28 20:33 ` |PENDING| " dpdklab
2024-09-28 20:37 ` |SUCCESS| " dpdklab
2024-09-28 20:39 ` dpdklab
2024-09-28 20:40 ` dpdklab
2024-09-28 20:40 ` |PENDING| " dpdklab
2024-09-28 20:43 ` |SUCCESS| pw144610 [RFC PATCH v12] " 0-day Robot
2024-09-28 20:59 ` |SUCCESS| pw144610 [PATCH] [RFC,v12] " dpdklab
2024-09-28 21:04 ` dpdklab [this message]
2024-09-28 21:36 ` dpdklab
2024-09-28 21:38 ` dpdklab
2024-09-28 21:39 ` dpdklab
2024-09-28 21:39 ` dpdklab
2024-09-28 22:58 ` dpdklab
2024-09-29 0:10 ` 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=66f86f64.050a0220.2d6ad7.d035SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=mb@smartsharesystems.com \
--cc=probb@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).