From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| [GIT MASTER] 93998f3c5f22747e4f2c5e8714fa5cbe6c9d1574
Date: Sat, 17 Feb 2024 17:24:19 -0800 (PST) [thread overview]
Message-ID: <65d15c43.920a0220.83f35.e503SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Performance Testing PASS_
Branch: dpdk
93998f3c5f22747e4f2c5e8714fa5cbe6c9d1574 --> 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 | 1.2% |
+------------+---------+----------+-------------+------------------------------+
| 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 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.3% |
+----------+-------------+---------+------------+------------------------------+
| 1 | 2 | 2048 | 64 | -3.6% |
+----------+-------------+---------+------------+------------------------------+
| 1 | 1 | 512 | 64 | -1.5% |
+----------+-------------+---------+------------+------------------------------+
| 1 | 1 | 2048 | 64 | -3.1% |
+----------+-------------+---------+------------+------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/28042/
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-18 1:24 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-18 1:24 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-18 3:13 dpdklab
2024-02-18 3:09 dpdklab
2024-02-18 2:47 dpdklab
2024-02-18 2:20 dpdklab
2024-02-18 2:19 dpdklab
2024-02-18 2:11 dpdklab
2024-02-18 2:04 dpdklab
2024-02-18 2:04 dpdklab
2024-02-18 2:01 dpdklab
2024-02-18 1:58 dpdklab
2024-02-18 1:57 dpdklab
2024-02-18 1:57 dpdklab
2024-02-18 1:54 dpdklab
2024-02-18 1:53 dpdklab
2024-02-18 1:53 dpdklab
2024-02-18 1:51 dpdklab
2024-02-18 1:47 dpdklab
2024-02-18 1:44 dpdklab
2024-02-18 1:43 dpdklab
2024-02-18 1:43 dpdklab
2024-02-18 1:42 dpdklab
2024-02-18 1:42 dpdklab
2024-02-18 1:41 dpdklab
2024-02-18 1:41 dpdklab
2024-02-18 1:41 dpdklab
2024-02-18 1:40 dpdklab
2024-02-18 1:40 dpdklab
2024-02-18 1:37 dpdklab
2024-02-18 1:36 dpdklab
2024-02-18 1:36 dpdklab
2024-02-18 1:36 dpdklab
2024-02-18 1:35 dpdklab
2024-02-18 1:34 dpdklab
2024-02-18 1:34 dpdklab
2024-02-18 1:34 dpdklab
2024-02-18 1:33 dpdklab
2024-02-18 1:30 dpdklab
2024-02-18 1:30 dpdklab
2024-02-18 1:30 dpdklab
2024-02-18 1:29 dpdklab
2024-02-18 1:29 dpdklab
2024-02-18 1:28 dpdklab
2024-02-18 1:26 dpdklab
2024-02-18 1:26 dpdklab
2024-02-18 1:25 dpdklab
2024-02-18 1:25 dpdklab
2024-02-18 1:25 dpdklab
2024-02-18 1:24 dpdklab
2024-02-18 1:24 dpdklab
2024-02-18 1:24 dpdklab
2024-02-18 1:23 dpdklab
2024-02-18 1:23 dpdklab
2024-02-18 1:22 dpdklab
2024-02-18 1:22 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=65d15c43.920a0220.83f35.e503SMTPIN_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).