Blazor time to first UI regression: blazorwasmbenchmark

[pr-benchmarks]

Scenario	Environment	Date	Old (ms)	New (ms)	Change	Dependencies
blazorwasmbenchmark		12/16/2022 06:53:54	227	242	6.84 % (16) 👎	Changes Name Version Diff

PowerBI Dashboard

[mkArtakMSFT]

@sebastienros when will these be closed? This one is a month old now.

[sebastienros]

I don't think I should close it unless I recognize the change (infrastructure, false positive, ...). This seems like an actual regression so IMO the product owner should own the decision.

I added the label yesterday (and it will now be set automatically) such that you can triage it more easily.

Do you want to change the workflow?

[MackinnonBuck]

Looks like the culprit is likely this dependency update PR: #45475.

That PR included some changes to Blazor WASM startup - perhaps those had an impact on startup time?

It should also be noted that, given that multiple dependencies were updated all at once (and this PR switched to the net8.0 runtime as well), it's possible that the root cause lies elsewhere.

/CC @pavelsavara

[pavelsavara]

That PR included some changes to Blazor WASM startup - perhaps those had an impact on startup time?

probably JS changes are not the problem. Upgrade itself could be.

@lewing do you have more hints ?

[lewing]

dotnet/runtime@1a37caf...caa0bd5 is over a month of changes from basically the start of .net8 till mid december, it could be so many things.

[lewing]

what browser+version are these tests running on?

[MackinnonBuck]

@lewing The tests are running on Chrome 108

[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.

[lewing]

These numbers are currently much better than they were I think we can close this