From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/DTS Bug 1969] dts: fix variance in single core forward performance test
Date: Thu, 16 Jul 2026 20:24:01 +0000 [thread overview]
Message-ID: <bug-1969-3@http.bugs.dpdk.org/> (raw)
http://bugs.dpdk.org/show_bug.cgi?id=1969
Bug ID: 1969
Summary: dts: fix variance in single core forward performance
test
Product: DPDK
Version: 26.07
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: DTS
Assignee: dev@dpdk.org
Reporter: abailey@iol.unh.edu
CC: juraj.linkes@pantheon.tech, probb@iol.unh.edu
Target Milestone: ---
Currently, multiple performance runs yield varying results with a standard
deviation of about 10Mpps. This is on the same testbed that has consistent
performance results when running old DTS with a standard deviation of about
1Mpps. There was a commit sent to old DTS specifically addressing this variance
issue by limiting the transmission duration to 5 seconds and averaging results
over a couple of runs instead of one. Testing this 5 second gap instead of 30
has shown consistent results when testing new DTS locally, however, averaging
over a few runs may be beneficial to implement as well with new DTS.
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2026-07-16 20:24 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=bug-1969-3@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--cc=dev@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.