automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw138407 [PATCH] build: build only one library type on Win
Date: Thu, 14 Mar 2024 13:46:03 -0700 (PDT)	[thread overview]
Message-ID: <65f3620b.170a0220.adddc.4db1SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <1710445477-23848-2-git-send-email-roretzla@linux.microsoft.com>

Test-Label: iol-intel-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/138407

_Performance Testing PASS_

Submitter: Tyler Retzlaff <roretzla@linux.microsoft.com>
Date: Thursday, March 14 2024 19:44:37 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:1c3d15933ac525dedfb3f15e7595baccc6d7174d

138407 --> performance testing pass

Test environment and result as below:

Ubuntu 20.04 ARM
Kernel: 4.15.0-132-generic
Compiler: gcc 7.5
NIC: Arm Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/2

Detail performance results: 
+------------+---------+----------+-------------+------------------------------+
| frame_size | txd/rxd | num_cpus | num_threads |  throughput difference from  |
|            |         |          |             |           expected           |
+============+=========+==========+=============+==============================+
| 64         | 512     | 1        | 1           | -0.6%                        |
+------------+---------+----------+-------------+------------------------------+
| 64         | 2048    | 1        | 1           | 0.4%                         |
+------------+---------+----------+-------------+------------------------------+

Ubuntu 20.04
Kernel: 4.15.0-generic
Compiler: gcc 7.4
NIC: Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/4

Detail performance results: 
+----------+-------------+---------+------------+------------------------------+
| num_cpus | num_threads | txd/rxd | frame_size |  throughput difference from  |
|          |             |         |            |           expected           |
+==========+=============+=========+============+==============================+
| 1        | 2           | 512     | 64         | 0.1%                         |
+----------+-------------+---------+------------+------------------------------+
| 1        | 2           | 2048    | 64         | -2.0%                        |
+----------+-------------+---------+------------+------------------------------+
| 1        | 1           | 512     | 64         | 1.1%                         |
+----------+-------------+---------+------------+------------------------------+
| 1        | 1           | 2048    | 64         | -2.0%                        |
+----------+-------------+---------+------------+------------------------------+

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-03-14 20:46 UTC|newest]

Thread overview: 70+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1710445477-23848-2-git-send-email-roretzla@linux.microsoft.com>
2024-03-14 19:22 ` |SUCCESS| pw138407 [PATCH] build: build only one library type on Windows qemudev
2024-03-14 19:26 ` qemudev
2024-03-14 19:46 ` checkpatch
2024-03-14 20:43 ` |FAILURE| " 0-day Robot
2024-03-14 20:45 ` |SUCCESS| pw138407 [PATCH] build: build only one library type on Win dpdklab
2024-03-14 20:46 ` dpdklab [this message]
2024-03-14 20:46 ` dpdklab
2024-03-14 20:47 ` dpdklab
2024-03-14 20:48 ` dpdklab
2024-03-14 20:48 ` dpdklab
2024-03-14 20:48 ` dpdklab
2024-03-14 20:49 ` dpdklab
2024-03-14 20:49 ` dpdklab
2024-03-14 20:49 ` dpdklab
2024-03-14 20:49 ` dpdklab
2024-03-14 20:50 ` dpdklab
2024-03-14 20:50 ` dpdklab
2024-03-14 20:50 ` dpdklab
2024-03-14 20:50 ` dpdklab
2024-03-14 20:50 ` dpdklab
2024-03-14 20:51 ` dpdklab
2024-03-14 20:51 ` dpdklab
2024-03-14 20:51 ` dpdklab
2024-03-14 20:51 ` dpdklab
2024-03-14 20:52 ` dpdklab
2024-03-14 20:52 ` dpdklab
2024-03-14 20:52 ` dpdklab
2024-03-14 20:52 ` dpdklab
2024-03-14 20:52 ` dpdklab
2024-03-14 20:53 ` dpdklab
2024-03-14 20:53 ` dpdklab
2024-03-14 20:53 ` dpdklab
2024-03-14 20:54 ` dpdklab
2024-03-14 20:54 ` dpdklab
2024-03-14 20:54 ` dpdklab
2024-03-14 20:54 ` dpdklab
2024-03-14 20:55 ` dpdklab
2024-03-14 20:55 ` dpdklab
2024-03-14 20:55 ` dpdklab
2024-03-14 20:55 ` dpdklab
2024-03-14 20:55 ` dpdklab
2024-03-14 20:55 ` dpdklab
2024-03-14 20:56 ` dpdklab
2024-03-14 20:56 ` dpdklab
2024-03-14 20:56 ` dpdklab
2024-03-14 20:56 ` dpdklab
2024-03-14 20:56 ` dpdklab
2024-03-14 20:57 ` dpdklab
2024-03-14 20:57 ` dpdklab
2024-03-14 20:57 ` dpdklab
2024-03-14 20:57 ` dpdklab
2024-03-14 20:57 ` dpdklab
2024-03-14 20:58 ` dpdklab
2024-03-14 20:58 ` dpdklab
2024-03-14 20:58 ` dpdklab
2024-03-14 20:58 ` dpdklab
2024-03-14 20:59 ` dpdklab
2024-03-14 20:59 ` dpdklab
2024-03-14 20:59 ` dpdklab
2024-03-14 20:59 ` dpdklab
2024-03-14 20:59 ` dpdklab
2024-03-14 20:59 ` dpdklab
2024-03-14 20:59 ` dpdklab
2024-03-14 21:03 ` dpdklab
2024-03-14 21:04 ` dpdklab
2024-03-14 21:06 ` dpdklab
2024-03-14 21:17 ` dpdklab
2024-03-14 21:27 ` dpdklab
2024-03-14 21:49 ` dpdklab
2024-03-14 23:34 ` 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=65f3620b.170a0220.adddc.4db1SMTPIN_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).