From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw136826-136832 [PATCH] [v3,7/7] compress/nitrox: add stat
Date: Thu, 15 Feb 2024 07:19:06 -0800 (PST) [thread overview]
Message-ID: <65ce2b6a.0d0a0220.53977.6314SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-mellanox-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/136832
_Performance Testing PASS_
Submitter: Nagadheeraj Rottela <rnagadheeraj@marvell.com>
Date: Thursday, February 15 2024 12:48:56
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:2b551097b3443ebf662e4d140600a4c9b108e73c
136826-136832 --> 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.2% |
+------------+---------+----------+-------------+------------------------------+
| 1024 | 256 | 1 | 1 | 0.2% |
+------------+---------+----------+-------------+------------------------------+
| 256 | 256 | 1 | 1 | -0.2% |
+------------+---------+----------+-------------+------------------------------+
| 1518 | 256 | 1 | 1 | 0.3% |
+------------+---------+----------+-------------+------------------------------+
| 512 | 256 | 1 | 1 | -0.3% |
+------------+---------+----------+-------------+------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29160/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-02-15 15:19 UTC|newest]
Thread overview: 67+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-15 15:19 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-15 16:05 dpdklab
2024-02-15 15:53 dpdklab
2024-02-15 15:46 dpdklab
2024-02-15 15:23 dpdklab
2024-02-15 15:07 dpdklab
2024-02-15 14:59 dpdklab
2024-02-15 14:55 dpdklab
2024-02-15 14:49 dpdklab
2024-02-15 14:31 dpdklab
2024-02-15 14:25 dpdklab
2024-02-15 14:15 dpdklab
2024-02-15 14:14 dpdklab
2024-02-15 14:13 dpdklab
2024-02-15 14:10 dpdklab
2024-02-15 14:10 dpdklab
2024-02-15 14:05 dpdklab
2024-02-15 14:05 dpdklab
2024-02-15 14:04 dpdklab
2024-02-15 14:02 dpdklab
2024-02-15 14:02 dpdklab
2024-02-15 14:01 dpdklab
2024-02-15 14:00 dpdklab
2024-02-15 13:58 dpdklab
2024-02-15 13:57 dpdklab
2024-02-15 13:56 dpdklab
2024-02-15 13:56 dpdklab
2024-02-15 13:55 dpdklab
2024-02-15 13:55 dpdklab
2024-02-15 13:55 dpdklab
2024-02-15 13:55 dpdklab
2024-02-15 13:53 dpdklab
2024-02-15 13:53 dpdklab
2024-02-15 13:52 dpdklab
2024-02-15 13:51 dpdklab
2024-02-15 13:51 dpdklab
2024-02-15 13:51 dpdklab
2024-02-15 13:51 dpdklab
2024-02-15 13:51 dpdklab
2024-02-15 13:51 dpdklab
2024-02-15 13:50 dpdklab
2024-02-15 13:50 dpdklab
2024-02-15 13:50 dpdklab
2024-02-15 13:49 dpdklab
2024-02-15 13:48 dpdklab
2024-02-15 13:48 dpdklab
2024-02-15 13:48 dpdklab
2024-02-15 13:43 dpdklab
2024-02-15 13:43 dpdklab
2024-02-15 13:42 dpdklab
2024-02-15 13:42 dpdklab
2024-02-15 13:41 dpdklab
2024-02-15 13:41 dpdklab
2024-02-15 13:39 dpdklab
2024-02-15 13:39 dpdklab
2024-02-15 13:38 dpdklab
2024-02-15 13:38 dpdklab
2024-02-15 13:37 dpdklab
2024-02-15 13:37 dpdklab
2024-02-15 13:37 dpdklab
2024-02-15 13:37 dpdklab
2024-02-15 13:36 dpdklab
2024-02-15 13:36 dpdklab
2024-02-15 13:35 dpdklab
2024-02-15 13:35 dpdklab
2024-02-15 13:34 dpdklab
2024-02-15 13:29 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=65ce2b6a.0d0a0220.53977.6314SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--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).