From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw130041-130043 [PATCH] [v8,3/3] telemetry: use standard l
Date: Thu, 10 Aug 2023 08:45:09 -0700 (PDT) [thread overview]
Message-ID: <64d50605.b00a0220.ebbf0.6f33SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-broadcom-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/130043
_Performance Testing PASS_
Submitter: Bruce Richardson <bruce.richardson@intel.com>
Date: Wednesday, August 09 2023 13:35:53
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:70b6941e4e22d67bc10495d1638234a7e974f582
130041-130043 --> performance testing pass
Test environment and result as below:
Ubuntu 22.04
Kernel: 5.15.0-39-generic
Compiler: gcc gcc (Ubuntu 11.2.0-19ubuntu1) 11.2.0
NIC: Broadcom Inc. and subsidiaries BCM57414 NetXtreme-E 10Gb/25Gb RDMA Ethernet Controller 16d7 25 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/3
Detail performance results:
+------------+---------+----------+-------------+------------------------------+
| frame_size | txd/rxd | num_cpus | num_threads | throughput difference from |
| | | | | expected |
+============+=========+==========+=============+==============================+
| 64 | 128 | 1 | 1 | 0.1% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 512 | 1 | 1 | -0.1% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 2048 | 1 | 1 | 0.2% |
+------------+---------+----------+-------------+------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/27263/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-08-10 15:45 UTC|newest]
Thread overview: 121+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-10 15:45 dpdklab [this message]
2023-08-10 15:53 dpdklab
2023-08-10 15:54 dpdklab
2023-08-10 15:58 dpdklab
2023-08-10 16:20 dpdklab
2023-08-10 16:47 dpdklab
2023-08-10 16:48 dpdklab
2023-08-10 16:51 dpdklab
2023-08-10 16:53 dpdklab
2023-08-10 16:54 dpdklab
2023-08-10 16:54 dpdklab
2023-08-10 16:54 dpdklab
2023-08-10 16:59 dpdklab
2023-08-10 16:59 dpdklab
2023-08-10 16:59 dpdklab
2023-08-10 17:00 dpdklab
2023-08-10 17:08 dpdklab
2023-08-10 17:16 dpdklab
2023-08-10 17:18 dpdklab
2023-08-10 17:18 dpdklab
2023-08-10 17:18 dpdklab
2023-08-10 17:21 dpdklab
2023-08-10 17:22 dpdklab
2023-08-10 17:30 dpdklab
2023-08-10 17:34 dpdklab
2023-08-10 17:35 dpdklab
2023-08-10 17:37 dpdklab
2023-08-10 17:38 dpdklab
2023-08-10 17:47 dpdklab
2023-08-10 17:58 dpdklab
2023-08-10 18:05 dpdklab
2023-08-10 18:07 dpdklab
2023-08-10 19:10 dpdklab
2023-08-10 19:43 dpdklab
2023-08-10 20:42 dpdklab
2023-08-10 20:53 dpdklab
2023-08-10 21:24 dpdklab
2023-08-10 21:24 dpdklab
2023-08-10 21:33 dpdklab
2023-08-10 21:34 dpdklab
2023-08-10 21:40 dpdklab
2023-08-10 21:42 dpdklab
2023-08-10 21:44 dpdklab
2023-08-10 21:44 dpdklab
2023-08-10 21:45 dpdklab
2023-08-10 21:45 dpdklab
2023-08-10 21:46 dpdklab
2023-08-10 21:46 dpdklab
2023-08-10 22:03 dpdklab
2023-08-10 22:06 dpdklab
2023-08-10 22:15 dpdklab
2023-08-10 22:16 dpdklab
2023-08-10 22:17 dpdklab
2023-08-10 22:17 dpdklab
2023-08-10 22:41 dpdklab
2023-08-11 2:46 dpdklab
2023-08-11 3:57 dpdklab
2023-08-11 4:03 dpdklab
2023-08-11 4:04 dpdklab
2023-08-11 4:04 dpdklab
2023-08-11 4:06 dpdklab
2023-08-11 4:07 dpdklab
2023-08-11 4:07 dpdklab
2023-08-11 4:09 dpdklab
2023-08-11 4:11 dpdklab
2023-08-11 4:15 dpdklab
2023-08-11 4:18 dpdklab
2023-08-11 4:21 dpdklab
2023-08-11 4:24 dpdklab
2023-08-11 4:25 dpdklab
2023-08-11 4:26 dpdklab
2023-08-11 4:27 dpdklab
2023-08-11 4:27 dpdklab
2023-08-11 4:38 dpdklab
2023-08-11 4:40 dpdklab
2023-08-11 4:41 dpdklab
2023-08-11 4:41 dpdklab
2023-08-11 4:49 dpdklab
2023-08-11 4:58 dpdklab
2023-08-11 4:58 dpdklab
2023-08-11 5:04 dpdklab
2023-08-11 5:08 dpdklab
2023-08-11 5:09 dpdklab
2023-08-11 5:14 dpdklab
2023-08-11 5:27 dpdklab
2023-08-11 5:27 dpdklab
2023-08-11 5:30 dpdklab
2023-08-11 5:30 dpdklab
2023-08-11 5:34 dpdklab
2023-08-11 5:38 dpdklab
2023-08-11 5:40 dpdklab
2023-08-11 5:41 dpdklab
2023-08-11 5:42 dpdklab
2023-08-11 5:43 dpdklab
2023-08-11 6:03 dpdklab
2023-08-11 6:24 dpdklab
2023-08-11 6:27 dpdklab
2023-08-11 8:49 dpdklab
2023-08-11 21:41 dpdklab
2023-08-11 21:42 dpdklab
2023-08-11 21:48 dpdklab
2023-08-11 21:48 dpdklab
2023-08-11 21:49 dpdklab
2023-08-11 21:49 dpdklab
2023-08-11 21:49 dpdklab
2023-08-11 21:49 dpdklab
2023-08-11 21:50 dpdklab
2023-08-11 23:08 dpdklab
2023-08-13 19:18 dpdklab
2023-08-13 22:20 dpdklab
2023-08-14 2:00 dpdklab
2023-08-14 2:01 dpdklab
2023-08-14 2:02 dpdklab
2023-08-14 2:03 dpdklab
2023-08-14 2:04 dpdklab
2023-08-14 2:04 dpdklab
2023-08-14 2:05 dpdklab
2023-08-14 2:06 dpdklab
2023-08-14 2:07 dpdklab
2023-08-14 2:10 dpdklab
2023-08-14 2:23 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=64d50605.b00a0220.ebbf0.6f33SMTPIN_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).