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| pw136009 [PATCH] mempool: test performance with larger bur
Date: Sun, 21 Jan 2024 02:23:58 -0800 (PST) [thread overview]
Message-ID: <65acf0be.050a0220.723ff.0920SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-mellanox-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/136009
_Performance Testing PASS_
Submitter: Morten Brorup <mb@smartsharesystems.com>
Date: Sunday, January 21 2024 04:52:49
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:515e1a4f4cddd33fcb35328a73449d30a8edfaf6
136009 --> 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.0% |
+------------+---------+----------+-------------+------------------------------+
| 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.2% |
+------------+---------+----------+-------------+------------------------------+
| 128 | 256 | 1 | 1 | 0.2% |
+------------+---------+----------+-------------+------------------------------+
| 1024 | 256 | 1 | 1 | -0.0% |
+------------+---------+----------+-------------+------------------------------+
| 256 | 256 | 1 | 1 | -0.2% |
+------------+---------+----------+-------------+------------------------------+
| 1518 | 256 | 1 | 1 | 0.0% |
+------------+---------+----------+-------------+------------------------------+
| 512 | 256 | 1 | 1 | -0.1% |
+------------+---------+----------+-------------+------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/28922/
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-21 10:24 UTC|newest]
Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-21 10:23 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-01-22 21:18 dpdklab
2024-01-22 21:11 dpdklab
2024-01-21 10:23 dpdklab
2024-01-21 9:33 dpdklab
2024-01-21 9:11 dpdklab
2024-01-21 9:09 dpdklab
2024-01-21 8:59 dpdklab
2024-01-21 8:52 dpdklab
2024-01-21 8:37 dpdklab
2024-01-21 8:34 dpdklab
2024-01-21 8:34 dpdklab
2024-01-21 8:33 dpdklab
2024-01-21 8:30 dpdklab
2024-01-21 8:28 dpdklab
2024-01-21 8:25 dpdklab
2024-01-21 8:24 dpdklab
2024-01-21 8:23 dpdklab
2024-01-21 8:23 dpdklab
2024-01-21 8:20 dpdklab
2024-01-21 8:20 dpdklab
2024-01-21 8:20 dpdklab
2024-01-21 8:18 dpdklab
2024-01-21 8:17 dpdklab
2024-01-21 8:17 dpdklab
2024-01-21 8:17 dpdklab
2024-01-21 8:14 dpdklab
2024-01-21 8:14 dpdklab
2024-01-21 8:14 dpdklab
2024-01-21 8:11 dpdklab
2024-01-21 8:06 dpdklab
2024-01-21 8:06 dpdklab
2024-01-21 8:04 dpdklab
2024-01-21 8:02 dpdklab
2024-01-21 7:56 dpdklab
2024-01-21 7:55 dpdklab
2024-01-21 7:54 dpdklab
2024-01-21 7:53 dpdklab
2024-01-21 7:44 dpdklab
2024-01-21 7:43 dpdklab
2024-01-21 7:43 dpdklab
2024-01-21 7:43 dpdklab
2024-01-21 7:42 dpdklab
2024-01-21 7:42 dpdklab
2024-01-21 7:42 dpdklab
2024-01-21 7:41 dpdklab
2024-01-21 7:27 dpdklab
2024-01-21 7:26 dpdklab
2024-01-21 7:25 dpdklab
2024-01-21 7:25 dpdklab
2024-01-21 7:24 dpdklab
2024-01-21 7:23 dpdklab
2024-01-21 7:23 dpdklab
2024-01-21 7:22 dpdklab
2024-01-21 7:22 dpdklab
2024-01-21 7:15 dpdklab
2024-01-21 7:14 dpdklab
2024-01-21 7:14 dpdklab
2024-01-21 7:11 dpdklab
2024-01-21 7:11 dpdklab
2024-01-21 7:10 dpdklab
2024-01-21 7:10 dpdklab
2024-01-21 7:00 dpdklab
2024-01-21 6:57 dpdklab
2024-01-21 6:56 dpdklab
2024-01-21 6:56 dpdklab
2024-01-21 6:55 dpdklab
2024-01-21 6:55 dpdklab
2024-01-21 6:55 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=65acf0be.050a0220.723ff.0920SMTPIN_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).