Blazor server performance improvements

[javiercn]

There are several performance improvements that we can make to reduce the bandwidth used by Blazor Server. Enabling compression requires us to investigate potential security issues with regards to HTTPS, packing the frames more tightly seems to offer a 30% improvement over the frame size, finally we can "minimize" some of our JS interop callbacks to reduce the size a bit further.

• Enable compression on blazorpack #35897
• For server-side Blazor, consider packing the reference frames more tightly #12306
• Reduce Data Flow #13025
• Shrink blazor.*.js file size, SignalR Minification #37260
• More integration for Blazor Server and SignalR #38109

[mkArtakMSFT]

Time-boxing this effort to M as it's not clear what this work is and some of the issues are separately tracked already.

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

We've moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process.

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

[SteveSandersonMS]

The only item remaining here is now tracked by #35897 so closing in favor of that.