Skip to content

WebAssembly runtime performance article #35700

@danroth27

Description

@danroth27

[EDIT by guardrex to add the metadata]

Edge has an Enhanced Security Mode feature that will run WebAssembly using an interpreter, which can negatively impact runtime performance. Developers that observe or see user reports of performance issues should consider adding an exception to opt-out of enhanced security mode for the site

I'm not sure where best to document this for Blazor users. Maybe somewhere in the Performance section? @guardrex Any suggestions?

UPDATE: Shifting to include ...

Instead of sticking this content about Edge Enhanced Security Mode here, how about we instead create a new article under the Performance node that specifically addresses WebAssembly runtime performance concerns? This article could cover the default JITerpriter based runtime vs AOT, the various AOT related performance options, like SIMD and exception handling support. This article would also link to the two new WebAssembly perf diagnostics articles for guidance on how to troubleshoot performance issues, making those articles potentially more discoverable.

SIMD coverage is currently here ...

https://learn.microsoft.com/en-us/aspnet/core/blazor/webassembly-build-tools-and-aot?view=aspnetcore-9.0#single-instruction-multiple-data-simd

Metadata

Metadata

Assignees

Type

No type

Projects

Status

Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions