From: dpdklab@iol.unh.edu
To: Ali Alnubani <alialnu@nvidia.com>, Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| [GIT MASTER] fbafb3676c482dab60c0b5465b47f2ea33893a36
Date: Fri, 21 Jul 2023 08:38:32 -0700 (PDT) [thread overview]
Message-ID: <64baa678.170a0220.4883d.5806SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Performance Testing PASS_
Branch: dpdk-next-virtio
fbafb3676c482dab60c0b5465b47f2ea33893a36 --> performance testing pass
Test environment and result as below:
Ubuntu 18.04
Kernel: 4.15.0-166-generic
Compiler: gcc 7.5.0
NIC: Mellanox ConnectX-5 100000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/6
Detail performance results:
+------------+---------+----------+-------------+------------------------------+
| frame_size | txd/rxd | num_cpus | num_threads | throughput difference from |
| | | | | expected |
+============+=========+==========+=============+==============================+
| 64 | 256 | 1 | 1 | -0.0% |
+------------+---------+----------+-------------+------------------------------+
| 128 | 256 | 1 | 1 | 0.0% |
+------------+---------+----------+-------------+------------------------------+
| 1024 | 256 | 1 | 1 | 0.1% |
+------------+---------+----------+-------------+------------------------------+
| 256 | 256 | 1 | 1 | -0.2% |
+------------+---------+----------+-------------+------------------------------+
| 1518 | 256 | 1 | 1 | 0.1% |
+------------+---------+----------+-------------+------------------------------+
| 512 | 256 | 1 | 1 | 0.1% |
+------------+---------+----------+-------------+------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/25567/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-07-21 15:38 UTC|newest]
Thread overview: 107+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-21 15:38 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-07-24 23:20 dpdklab
2023-07-24 23:20 dpdklab
2023-07-24 3:04 dpdklab
2023-07-24 2:59 dpdklab
2023-07-24 2:49 dpdklab
2023-07-24 2:44 dpdklab
2023-07-24 2:40 dpdklab
2023-07-22 3:48 dpdklab
2023-07-22 2:04 dpdklab
2023-07-22 2:01 dpdklab
2023-07-22 1:46 dpdklab
2023-07-22 1:33 dpdklab
2023-07-22 1:25 dpdklab
2023-07-22 1:22 dpdklab
2023-07-22 1:21 dpdklab
2023-07-22 1:20 dpdklab
2023-07-22 1:19 dpdklab
2023-07-22 1:18 dpdklab
2023-07-22 1:16 dpdklab
2023-07-22 1:12 dpdklab
2023-07-22 1:08 dpdklab
2023-07-22 1:07 dpdklab
2023-07-22 1:06 dpdklab
2023-07-22 1:03 dpdklab
2023-07-22 1:02 dpdklab
2023-07-22 1:02 dpdklab
2023-07-22 1:01 dpdklab
2023-07-21 18:36 dpdklab
2023-07-21 17:44 dpdklab
2023-07-21 17:38 dpdklab
2023-07-21 16:45 dpdklab
2023-07-21 16:04 dpdklab
2023-07-21 16:03 dpdklab
2023-07-21 16:02 dpdklab
2023-07-21 15:59 dpdklab
2023-07-21 15:55 dpdklab
2023-07-21 15:50 dpdklab
2023-07-21 15:42 dpdklab
2023-07-21 15:40 dpdklab
2023-07-21 15:39 dpdklab
2023-07-21 15:37 dpdklab
2023-07-21 15:36 dpdklab
2023-07-21 15:34 dpdklab
2023-07-21 15:33 dpdklab
2023-07-21 3:50 dpdklab
2023-07-21 3:05 dpdklab
2023-07-21 2:51 dpdklab
2023-07-21 2:48 dpdklab
2023-07-21 2:43 dpdklab
2023-07-21 2:38 dpdklab
2023-07-21 2:34 dpdklab
2023-07-21 2:13 dpdklab
2023-07-21 2:12 dpdklab
2023-07-21 2:09 dpdklab
2023-07-21 2:05 dpdklab
2023-07-21 1:46 dpdklab
2023-07-21 1:26 dpdklab
2023-07-21 1:21 dpdklab
2023-07-21 1:21 dpdklab
2023-07-21 1:18 dpdklab
2023-07-21 1:17 dpdklab
2023-07-21 1:15 dpdklab
2023-07-21 1:12 dpdklab
2023-07-21 1:12 dpdklab
2023-07-21 1:09 dpdklab
2023-07-21 1:07 dpdklab
2023-07-21 1:07 dpdklab
2023-07-21 1:07 dpdklab
2023-07-21 1:07 dpdklab
2023-07-21 1:06 dpdklab
2023-07-21 1:06 dpdklab
2023-07-20 23:08 dpdklab
2023-07-20 23:03 dpdklab
2023-07-20 22:52 dpdklab
2023-07-20 22:48 dpdklab
2023-07-20 22:31 dpdklab
2023-07-20 21:45 dpdklab
2023-07-20 21:41 dpdklab
2023-07-20 21:24 dpdklab
2023-07-20 21:20 dpdklab
2023-07-20 21:11 dpdklab
2023-07-20 21:10 dpdklab
2023-07-20 19:56 dpdklab
2023-07-20 19:06 dpdklab
2023-07-20 19:01 dpdklab
2023-07-20 18:49 dpdklab
2023-07-20 18:37 dpdklab
2023-07-20 18:37 dpdklab
2023-07-20 18:36 dpdklab
2023-07-20 18:36 dpdklab
2023-07-20 18:33 dpdklab
2023-07-20 18:33 dpdklab
2023-07-20 18:31 dpdklab
2023-07-20 18:31 dpdklab
2023-07-20 17:24 dpdklab
2023-07-20 17:23 dpdklab
2023-07-20 17:23 dpdklab
2023-07-20 16:13 dpdklab
2023-07-20 16:06 dpdklab
2023-07-20 15:55 dpdklab
2023-07-20 15:53 dpdklab
2023-07-20 15:53 dpdklab
2023-07-20 15:52 dpdklab
2023-07-20 15:52 dpdklab
2023-07-20 15:43 dpdklab
2023-07-20 15:42 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=64baa678.170a0220.4883d.5806SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=alialnu@nvidia.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).