Skip to content

Update performance notes for SetParametersAsync method#37061

Merged
guardrex merged 7 commits intomainfrom
guardrex-patch-6
Apr 28, 2026
Merged

Update performance notes for SetParametersAsync method#37061
guardrex merged 7 commits intomainfrom
guardrex-patch-6

Conversation

@guardrex
Copy link
Copy Markdown
Collaborator

@guardrex guardrex commented Apr 28, 2026

Fixes #35507

Thanks @hakenr! 🎷

Wade/Tom ... Just need one review to get this one in.

Clarified the performance improvement potential of overriding SetParametersAsync, noting it typically yields under 10% improvement in .NET 10.

Notes ...

  • I'm using the HTML named entity for the em dash because the GH markdown editor doesn't make it clear that the character is indeed an em dash.
  • I'm going to peg the "current release" remark at .NET 10 because we don't know how this might change in the future and the "current release" could be anything when the content targets >=8.0. Benchmark testing was performed for .NET 10, so we can only state the figures for that release.
  • This must be versioned because "Interactive Server" has no meaning prior to .NET 8.

Internal previews

📄 File 🔗 Preview link
aspnetcore/blazor/performance/rendering.md aspnetcore/blazor/performance/rendering

Clarified the performance improvement potential of overriding SetParametersAsync, noting it typically yields under 10% improvement in .NET 10.
@guardrex guardrex self-assigned this Apr 28, 2026
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Updates the Blazor rendering performance guidance to clarify the (reduced) benefit of manually overriding SetParametersAsync in newer ASP.NET Core/Blazor versions.

Changes:

  • Adds monikered guidance for >= aspnetcore-8.0 that characterizes the typical performance gains as small (benchmarked on .NET 10).
  • Retains the prior (larger) performance improvement guidance for < aspnetcore-8.0.

Comment thread aspnetcore/blazor/performance/rendering.md Outdated
Comment thread aspnetcore/blazor/performance/rendering.md Outdated
@guardrex
Copy link
Copy Markdown
Collaborator Author

guardrex commented Apr 28, 2026

Sorry for all of the update pings, @hakenr. The lingo is a bit tricky. I think I have it now ... or close to what we'll go with. Please feel free to suggest updates. Wade or Tom will be along shortly to review, and then we'll get this merged. Thanks again!

Add AI usage note to Blazor rendering performance article.
Copy link
Copy Markdown
Member

@hakenr hakenr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

Comment thread aspnetcore/blazor/performance/rendering.md Outdated
Copy link
Copy Markdown
Contributor

@wadepickett wadepickett left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks great, approved.

Co-authored-by: Wade Pickett <wpickett@microsoft.com>
@guardrex guardrex merged commit 8ff2f3e into main Apr 28, 2026
4 checks passed
@guardrex guardrex deleted the guardrex-patch-6 branch April 28, 2026 20:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Blazor] Rendering performance - Implement SetParametersAsync manually still valid?

4 participants