automatic DPDK test reports
 help / color / mirror / Atom feed
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| pw146178 [PATCH] [RESEND] malloc: fix allocation for a spe
Date: Thu, 17 Oct 2024 19:33:43 -0700 (PDT)	[thread overview]
Message-ID: <6711c907.630a0220.e0d64.1193SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20241017100207.1207-1-artur.paszkiewicz@intel.com>

Test-Label: iol-mellanox-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/146178

_Performance Testing PASS_

Submitter: Artur Paszkiewicz <artur.paszkiewicz@intel.com>
Date: Thursday, October 17 2024 10:02:06 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:74efd38b416fcf9eae2a5b429b81b550a73a47b6

146178 --> performance testing pass

Upstream job id: Template-DTS-Pipeline#189001

Test environment and result as below:

Ubuntu 24.04
Kernel: 6.8.0-45-generic
Compiler: gcc 13.2.0
NIC: NVIDIA Mellanox ConnectX-7 100000 Mbps
Fail/Total: 0/6

Detail performance results: 
+------------+---------+----------+-------------+------------------------------+
| frame_size | txd/rxd | num_cpus | num_threads |  throughput difference from  |
|            |         |          |             |           expected           |
+============+=========+==========+=============+==============================+
| 64         | 1024    | 1        | 1           | -0.1%                        |
+------------+---------+----------+-------------+------------------------------+
| 128        | 1024    | 1        | 1           | 0.0%                         |
+------------+---------+----------+-------------+------------------------------+
| 256        | 1024    | 1        | 1           | 0.9%                         |
+------------+---------+----------+-------------+------------------------------+
| 512        | 1024    | 1        | 1           | 0.1%                         |
+------------+---------+----------+-------------+------------------------------+
| 1024       | 1024    | 1        | 1           | 0.1%                         |
+------------+---------+----------+-------------+------------------------------+
| 1518       | 1024    | 1        | 1           | -0.3%                        |
+------------+---------+----------+-------------+------------------------------+

Ubuntu 24.04
Kernel: 6.8.0-45-generic
Compiler: gcc 13.2.0
NIC: Mellanox ConnectX-6 Lx 25000 Mbps
Fail/Total: 0/6

Detail performance results: 
+------------+---------+----------+-------------+------------------------------+
| frame_size | txd/rxd | num_cpus | num_threads |  throughput difference from  |
|            |         |          |             |           expected           |
+============+=========+==========+=============+==============================+
| 64         | 1024    | 1        | 1           | -0.0%                        |
+------------+---------+----------+-------------+------------------------------+
| 128        | 1024    | 1        | 1           | -0.1%                        |
+------------+---------+----------+-------------+------------------------------+
| 256        | 1024    | 1        | 1           | -0.0%                        |
+------------+---------+----------+-------------+------------------------------+
| 512        | 1024    | 1        | 1           | -0.0%                        |
+------------+---------+----------+-------------+------------------------------+
| 1024       | 1024    | 1        | 1           | 0.3%                         |
+------------+---------+----------+-------------+------------------------------+
| 1518       | 1024    | 1        | 1           | 0.2%                         |
+------------+---------+----------+-------------+------------------------------+

To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/31530/

UNH-IOL DPDK Community Lab

To manage your email subscriptions, visit: 
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/

  parent reply	other threads:[~2024-10-18  2:33 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20241017100207.1207-1-artur.paszkiewicz@intel.com>
2024-10-17  9:35 ` |SUCCESS| pw146178 [PATCH RESEND] malloc: fix allocation for a specific case with ASan qemudev
2024-10-17  9:39 ` qemudev
2024-10-17 10:03 ` checkpatch
2024-10-17 11:03 ` 0-day Robot
2024-10-17 22:28 ` |SUCCESS| pw146178 [PATCH] [RESEND] malloc: fix allocation for a spe dpdklab
2024-10-17 22:40 ` dpdklab
2024-10-17 23:05 ` dpdklab
2024-10-18  0:59 ` |PENDING| " dpdklab
2024-10-18  1:52 ` dpdklab
2024-10-18  2:33 ` dpdklab [this message]
2024-10-18  3:32 ` |FAILURE| " dpdklab
2024-10-18  3:46 ` |SUCCESS| " dpdklab
2024-10-18  4:19 ` |PENDING| " dpdklab
2024-10-18  4:41 ` |FAILURE| " dpdklab
2024-10-18  4:42 ` dpdklab
2024-10-18  6:46 ` |SUCCESS| " dpdklab
2024-10-18  6:53 ` dpdklab
2024-10-18  7:12 ` dpdklab
2024-10-18  7:26 ` dpdklab
2024-10-18  7:57 ` dpdklab
2024-10-18 11:04 ` |FAILURE| " dpdklab
2024-10-18 11:07 ` |SUCCESS| " dpdklab
2024-10-20 11:16 ` dpdklab
2024-10-23  6:17 ` dpdklab
2024-10-23 11:52 ` dpdklab
2024-10-23 16:53 ` dpdklab
2024-10-23 17:19 ` dpdklab
2024-10-23 18:14 ` dpdklab
2024-10-23 20:04 ` 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=6711c907.630a0220.e0d64.1193SMTPIN_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).