[Blazor WASM AOT]: Add Wasm + AOT to benchmarks

[pranavkm]

[ghost]

Thanks for contacting us. We're moving this issue to the Next sprint planning milestone for future evaluation / consideration. We will evaluate the request when we are planning the work for the next milestone. To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

[pranavkm]

Finally got around to this, but I'm running in to a fun issue with running our benchmarks with AOT enabled:

blazor.webassembly.js:1 
        
RuntimeError: null function or function signature mismatch
    at dotnet.wasm:0x9eabca
    at dotnet.wasm:0xa1941e
    at dotnet.wasm:0xcc663
    at dotnet.wasm:0xcc4b7
    at dotnet.wasm:0xcc3e6
    at dotnet.wasm:0x342b00
    at dotnet.wasm:0x33755
    at dotnet.wasm:0xae129d
    at invoke_vi (dotnet.7.0.0-alpha.1.21551.1.aet831yga1.js:1)
    at dotnet.wasm:0xc783e8
callEntryPoint @ blazor.webassembly.js:1
await in callEntryPoint (async)
Nt @ blazor.webassembly.js:1
await in Nt (async)
(anonymous) @ blazor.webassembly.js:1
(anonymous) @ blazor.webassembly.js:1

@radical would you be able to help figure this out? I have the publish output of my app here: https://microsoft-my.sharepoint.com/:u:/p/prkrishn/Eawjp_sR6VlLstzAby1hJ6QBH2VL2Y9JE3aYr72X51FIAA?e=EfixgO, branch with my changes are here: https://github.com/pranavkm/aspnetcore/tree/prkrishn/aot-tests

[ghost]

Thanks for contacting us.

We're moving this issue to the .NET 7 Planning milestone for future evaluation / consideration. We would like to keep this around to collect more feedback, which can help us with prioritizing this work. We will re-evaluate this issue, during our next planning meeting(s). If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues. To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

[SamMonoRT]

cc @lewing

[ghost]

Thanks for contacting us.

We're moving this issue to the .NET 8 Planning milestone for future evaluation / consideration. We would like to keep this around to collect more feedback, which can help us with prioritizing this work. We will re-evaluate this issue, during our next planning meeting(s). If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues. To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

[radical]

If anyone picks this up, and is having issues with AOT then I can help with that.

[ghost]

Thanks for contacting us.

We're moving this issue to the .NET 8 Planning milestone for future evaluation / consideration. We would like to keep this around to collect more feedback, which can help us with prioritizing this work. We will re-evaluate this issue, during our next planning meeting(s). If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues. To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

[ghost]

Thanks for contacting us.

We're moving this issue to the .NET 9 Planning milestone for future evaluation / consideration. We would like to keep this around to collect more feedback, which can help us with prioritizing this work. We will re-evaluate this issue, during our next planning meeting(s). If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues. To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

[SamMonoRT]

cc @lewing @mkArtakMSFT - this keeps moving from .NET7 to NET8 to NET9, and other than microbenchmarks we don't quite have startup/rendering scenarios for AOT WASM automated in the labs. Any thoughts?

[lewing]

@steveisok and I talked about doing startup tests on mobile for wasm, we should plan for that to happen still

[ghost]

Thanks for contacting us.

We're moving this issue to the .NET 9 Planning milestone for future evaluation / consideration. We would like to keep this around to collect more feedback, which can help us with prioritizing this work. We will re-evaluate this issue, during our next planning meeting(s). If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues. To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.