From: Manit Mahajan <mmahajan@iol.unh.edu>
To: anatoly.burakov@intel.com
Cc: ci@dpdk.org, bruce.richardson@intel.com, honnappa.nagarahalli@arm.com
Subject: Intel E810 Performance Regression - ARM Grace Server
Date: Wed, 2 Jul 2025 17:09:38 -0400 [thread overview]
Message-ID: <CANcZauy3M493tMNd+1w+o3OMwYwAMENnrfWuM7vJQHqW9knXmA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1689 bytes --]
Hi we have an update about the single core forwarding test on the ARM Grace
server with the E810 100G Ice card. There was an intel PMDs series that was
merged a week ago which had some performance failures when it was going
through the CI:
https://patches.dpdk.org/project/dpdk/patch/01c94afcb0b1c2795c031afc872a8faf3f0db2b5.1749229651.git.anatoly.burakov@intel.com/
and: http://mails.dpdk.org/archives/test-report/2025-June/883654.html
As you can see it causes roughly a 6% decrease in packets forwarded in the
single core forwarding test with 64Byte frames and 512 txd/rxd. The delta
tolerance on the single core forwarding test is 5%, so a 6% reduction in
MPPS forwarded is a failure.
This was merged into mainline 6 days ago, which is why some failures
started to come in this week for the E810 Grace test.
To double check this, on DPDK I checked out to:
test/event: fix event vector adapter timeouts
(2eca0f4cd5daf6cd54b8705f6f76f3003c923912) which directly precedes the
Intel PMD patchseries, and ran the test and it forwarded the pre-regression
MPPS that we expected.
Then I checked out to net/intel: add common Tx mbuf recycle
(f5fd081c86ae415515ab55cbacf10c9c50536ca1)
and I ran the test and it had the 6% reduction in MPPS forwarded.
Another thing to note is that regrettably the ARM Grace E810 test did not
get run on the v7 (the final version) of this series, which meant the
failure was not displayed on that version and that's probably why it was
merged. We will look back into our job history and see why this test failed
to report.
Please let me know if you have any questions about the test, the testbed
environment info, or anything else.
Thanks,
Manit Mahajan
[-- Attachment #2: Type: text/html, Size: 2022 bytes --]
next reply other threads:[~2025-07-02 21:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-02 21:09 Manit Mahajan [this message]
2025-07-03 7:03 ` Honnappa Nagarahalli
2025-07-03 8:42 ` Richardson, Bruce
2025-07-03 12:53 ` Patrick Robb
2025-07-03 13:11 ` Richardson, Bruce
2025-07-03 15:21 ` Manit Mahajan
2025-07-03 15:22 ` Richardson, Bruce
2025-07-03 15:20 ` Patrick Robb
2025-07-03 15:30 ` Richardson, Bruce
2025-07-03 15:31 ` Manit Mahajan
2025-07-03 15:39 ` Richardson, Bruce
2025-07-03 17:38 ` Patrick Robb
2025-07-03 18:54 ` Mcnamara, John
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=CANcZauy3M493tMNd+1w+o3OMwYwAMENnrfWuM7vJQHqW9knXmA@mail.gmail.com \
--to=mmahajan@iol.unh.edu \
--cc=anatoly.burakov@intel.com \
--cc=bruce.richardson@intel.com \
--cc=ci@dpdk.org \
--cc=honnappa.nagarahalli@arm.com \
/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).