From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw129111 [PATCH] doc: ensure sphinx output is reproducible
Date: Thu, 29 Jun 2023 06:48:33 -0700 (PDT) [thread overview]
Message-ID: <649d8bb1.0d0a0220.4e2b4.7b3fSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-intel-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/129111
_Performance Testing PASS_
Submitter: Christian Ehrhardt <christian.ehrhardt@canonical.com>
Date: Thursday, June 29 2023 12:58:35
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:93a4b3beba4ee611685148917981f846427cafb2
129111 --> 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.1% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 2048 | 1 | 1 | 0.5% |
+------------+---------+----------+-------------+------------------------------+
Ubuntu 20.04
Kernel: 4.15.0-generic
Compiler: gcc 7.4
NIC: Intel Corporation Ethernet Converged Network Adapter 82599ES 10000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/6
Detail performance results:
+----------+-------------+---------+------------+------------------------------+
| num_cpus | num_threads | txd/rxd | frame_size | throughput difference from |
| | | | | expected |
+==========+=============+=========+============+==============================+
| 1 | 2 | 128 | 64 | 0.0% |
+----------+-------------+---------+------------+------------------------------+
| 1 | 2 | 512 | 64 | -0.2% |
+----------+-------------+---------+------------+------------------------------+
| 1 | 2 | 2048 | 64 | -0.0% |
+----------+-------------+---------+------------+------------------------------+
| 1 | 1 | 128 | 64 | -0.2% |
+----------+-------------+---------+------------+------------------------------+
| 1 | 1 | 512 | 64 | 0.0% |
+----------+-------------+---------+------------+------------------------------+
| 1 | 1 | 2048 | 64 | -0.1% |
+----------+-------------+---------+------------+------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/26864/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-06-29 13:48 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-29 13:48 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-06-30 23:33 dpdklab
2023-06-30 0:21 dpdklab
2023-06-30 0:05 dpdklab
2023-06-30 0:00 dpdklab
2023-06-29 23:56 dpdklab
2023-06-29 23:45 dpdklab
2023-06-29 14:58 dpdklab
2023-06-29 14:36 dpdklab
2023-06-29 14:26 dpdklab
2023-06-29 14:26 dpdklab
2023-06-29 14:26 dpdklab
2023-06-29 14:23 dpdklab
2023-06-29 14:19 dpdklab
2023-06-29 14:06 dpdklab
2023-06-29 14:03 dpdklab
2023-06-29 13:58 dpdklab
2023-06-29 13:48 dpdklab
2023-06-29 13:48 dpdklab
2023-06-29 13:48 dpdklab
2023-06-29 13:48 dpdklab
2023-06-29 13:48 dpdklab
2023-06-29 13:48 dpdklab
2023-06-29 13:48 dpdklab
2023-06-29 13:48 dpdklab
2023-06-29 13:46 dpdklab
2023-06-29 13:45 dpdklab
2023-06-29 13:45 dpdklab
2023-06-29 13:45 dpdklab
2023-06-29 13:45 dpdklab
2023-06-29 13:44 dpdklab
[not found] <20230629125838.1995751-1-christian.ehrhardt@canonical.com>
2023-06-29 12:46 ` qemudev
2023-06-29 12:50 ` qemudev
2023-06-29 13:00 ` checkpatch
2023-06-29 14:19 ` 0-day Robot
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=649d8bb1.0d0a0220.4e2b4.7b3fSMTPIN_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).