From: dpdklab@iol.unh.edu
To: Ajit Khaparde <ajit.khaparde@broadcom.com>,
Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| [GIT MASTER] bab4318634e0d2276e8bae5ea18789cfda813c70
Date: Sun, 16 Jan 2022 06:00:59 +0000 (UTC) [thread overview]
Message-ID: <20220116060059.70836602B7@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 1576 bytes --]
_Performance Testing PASS_
Branch: tags/v20.11
bab4318634e0d2276e8bae5ea18789cfda813c70 --> performance testing pass
Test environment and result as below:
Ubuntu 20.04
Kernel: 4.15.0-65-generic
Compiler: gcc gcc (Ubuntu 7.4.0-1ubuntu1~18.04.1) 7.4.0
NIC: Broadcom Inc. brcm_57414 25000 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 | -0.1% |
+----------+-------------+---------+------------+------------------------------+
| 1 | 1 | 512 | 64 | -0.2% |
+----------+-------------+---------+------------+------------------------------+
| 1 | 1 | 2048 | 64 | -0.1% |
+----------+-------------+---------+------------+------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/18288/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2022-01-16 6:01 UTC|newest]
Thread overview: 73+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-16 6:00 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-01-17 6:50 dpdklab
2022-01-17 6:44 dpdklab
2022-01-17 6:35 dpdklab
2022-01-17 6:10 dpdklab
2022-01-17 6:00 dpdklab
2022-01-17 6:00 dpdklab
2022-01-17 5:58 dpdklab
2022-01-17 5:55 dpdklab
2022-01-17 5:53 dpdklab
2022-01-17 5:51 dpdklab
2022-01-17 5:49 dpdklab
2022-01-17 5:45 dpdklab
2022-01-17 5:45 dpdklab
2022-01-16 7:17 dpdklab
2022-01-16 7:03 dpdklab
2022-01-16 6:34 dpdklab
2022-01-16 6:13 dpdklab
2022-01-16 6:01 dpdklab
2022-01-16 5:59 dpdklab
2022-01-16 5:59 dpdklab
2022-01-16 5:54 dpdklab
2022-01-16 5:52 dpdklab
2022-01-16 5:49 dpdklab
2022-01-16 5:46 dpdklab
2022-01-16 5:45 dpdklab
2022-01-15 8:34 dpdklab
2022-01-15 6:43 dpdklab
2022-01-15 6:29 dpdklab
2022-01-15 6:10 dpdklab
2022-01-15 6:01 dpdklab
2022-01-15 6:01 dpdklab
2022-01-15 5:59 dpdklab
2022-01-15 5:59 dpdklab
2022-01-15 5:55 dpdklab
2022-01-15 5:54 dpdklab
2022-01-15 5:52 dpdklab
2022-01-15 5:49 dpdklab
2022-01-15 5:45 dpdklab
2022-01-14 7:27 dpdklab
2022-01-14 7:03 dpdklab
2022-01-14 6:35 dpdklab
2022-01-14 6:14 dpdklab
2022-01-14 6:02 dpdklab
2022-01-14 6:01 dpdklab
2022-01-14 6:01 dpdklab
2022-01-14 6:00 dpdklab
2022-01-14 5:59 dpdklab
2022-01-14 5:55 dpdklab
2022-01-14 5:51 dpdklab
2022-01-14 5:49 dpdklab
2022-01-14 5:48 dpdklab
2022-01-13 7:19 dpdklab
2022-01-13 6:54 dpdklab
2022-01-13 6:45 dpdklab
2022-01-13 6:12 dpdklab
2022-01-13 6:02 dpdklab
2022-01-13 6:01 dpdklab
2022-01-13 6:00 dpdklab
2022-01-13 6:00 dpdklab
2022-01-13 5:54 dpdklab
2022-01-13 5:52 dpdklab
2022-01-13 5:51 dpdklab
2022-01-13 5:46 dpdklab
2022-01-13 5:46 dpdklab
2022-01-12 20:44 dpdklab
2022-01-12 19:49 dpdklab
2022-01-12 19:39 dpdklab
2022-01-12 19:13 dpdklab
2022-01-12 19:01 dpdklab
2022-01-12 18:56 dpdklab
2022-01-12 18:56 dpdklab
2022-01-12 18:50 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=20220116060059.70836602B7@dpdk-ubuntu.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=ajit.khaparde@broadcom.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).