test suite reviews and discussions
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dts@dpdk.org
Subject: [DTS/tests Bug 1507] Fixed test traffic patterns make test results unreliable
Date: Tue, 30 Jul 2024 10:14:00 +0000	[thread overview]
Message-ID: <bug-1507-433@http.bugs.dpdk.org/> (raw)

[-- Attachment #1: Type: text/plain, Size: 1543 bytes --]

https://bugs.dpdk.org/show_bug.cgi?id=1507

            Bug ID: 1507
           Summary: Fixed test traffic patterns make test results
                    unreliable
           Product: DTS
           Version: unspecified
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: major
          Priority: Normal
         Component: tests
          Assignee: dts@dpdk.org
          Reporter: mb@smartsharesystems.com
  Target Milestone: ---

It has recently come to my attention that a lot of testing is performed with
fixed packet size and type.

This has two bad consequences:

1. The same code path in the SUT is taken every time.
This is bad, because it reduces the code coverage of functional testing.
Worst case, newly added code (intended to be tested) may be in a non-taken code
path, and thus not tested at all.

2. When the same code path is taken every time, the CPU's branch predictor
achieves near-perfect hit rate, and thus the performance test results do not
reflect real-life performance.
This is very bad, because performance results are often used to quantify the
benefit of suggested performance optimizations, and they might in fact have the
opposite effect in real life (with real-life traffic mix).

Testing should be performed with a realistic mix of packets, as seen on the
internet.
For some cases, packet size matters, and for some cases, packet type matters.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #2: Type: text/html, Size: 3406 bytes --]

                 reply	other threads:[~2024-07-30 11:16 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-1507-433@http.bugs.dpdk.org/ \
    --to=bugzilla@dpdk.org \
    --cc=dts@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).