From: Ajit Khaparde <ajit.khaparde@broadcom.com>
To: Patrick Robb <probb@iol.unh.edu>
Cc: ci@dpdk.org
Subject: Re: BRCM 57414 Performance Test
Date: Thu, 14 Mar 2024 09:08:12 -0700 [thread overview]
Message-ID: <CACZ4nhuGpjXtobGxesSv5XM=UQE48ZjDmXWR9Ss0EhUGeaoJ1g@mail.gmail.com> (raw)
In-Reply-To: <CAJvnSUBhhaLukfC7ECKG2RWUNjq4rqRvOXBdjVRSdtXwGgKfyg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1694 bytes --]
Hi Patrick,
Yes, it makes sense.
Thanks for the note. Please let me know once its sorted out.
Thanks
Ajit
On Thu, Mar 14, 2024 at 7:46 AM Patrick Robb <probb@iol.unh.edu> wrote:
>
> Hi Ajit,
>
> One of the tests we run for the BRCM 57414 NIC in the dpdk community
> lab is a single core forwarding test in which we try to match line
> rate on the NIC, and protect against any performance regressions in
> DPDK. We track the MPPS forwarded between interfaces on the DUT,
> compare that metric against the most recent "baseline" run, and if the
> delta is more than 5% it is a fail. So the idea is if a significant
> regression is introduced on a patch, CI testing catches that.
>
> Right now on one of our ARM systems with brcm57414 this test is having
> high variance... more than the 5% threshold in some cases. I think
> this may in some way relate to the maintenance we did a few weeks back
> - we were seeing like .2% variance before. The expected throughput
> seems consistent, but the results have higher variance than normal.
> Obviously something is slightly wrong, and the system needs to be
> re-tuned a little or something. We can look at it (prefer to do any
> maintenance once all RCs are complete), but in the interim I want to
> just bump the accepted Delta from 5% to 7%, just to stop the false
> fails, but still maintain some coverage. Once we tune the system and
> reduce the results variance, we can return to 5%.
>
> Does this sound fine to you?
>
> Thanks,
> Patrick
>
> --
> Patrick Robb
>
> Technical Service Manager
>
> UNH InterOperability Laboratory
>
> 21 Madbury Rd, Suite 100, Durham, NH 03824
>
> www.iol.unh.edu
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4218 bytes --]
prev parent reply other threads:[~2024-03-14 16:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-14 14:45 Patrick Robb
2024-03-14 16:08 ` Ajit Khaparde [this message]
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='CACZ4nhuGpjXtobGxesSv5XM=UQE48ZjDmXWR9Ss0EhUGeaoJ1g@mail.gmail.com' \
--to=ajit.khaparde@broadcom.com \
--cc=ci@dpdk.org \
--cc=probb@iol.unh.edu \
/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).