Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

For server-side Blazor, consider packing the reference frames more tightly #12306

Closed
SteveSandersonMS opened this issue Jul 18, 2019 · 2 comments
Closed

For server-side Blazor, consider packing the reference frames more tightly #12306

SteveSandersonMS opened this issue Jul 18, 2019 · 2 comments
Labels
affected-most This issue impacts most of the customers area-blazor Includes: Blazor, Razor Components enhancement This issue represents an ask for new feature or an enhancement to an existing one feature-blazor-server Pillar: Technical Debt reevaluate We need to reevaluate the issue and make a decision about it severity-nice-to-have This label is used by an internal tool
Milestone
.NET 9 Planning

Comments

@SteveSandersonMS
Copy link
Member

Currently, RenderBatchWriter uses 20 bytes per frame. It could be reduced to 14 bytes per frame via non-breaking changes as described in https://github.com/aspnet/AspNetCore/pull/12305/files#r304891742
@SteveSandersonMS SteveSandersonMS added the area-blazor Includes: Blazor, Razor Components label Jul 18, 2019
@SteveSandersonMS SteveSandersonMS added this to the Backlog milestone Jul 18, 2019
@SteveSandersonMS SteveSandersonMS mentioned this issue Jul 18, 2019
Merged
@SteveSandersonMS SteveSandersonMS added affected-most This issue impacts most of the customers enhancement This issue represents an ask for new feature or an enhancement to an existing one severity-nice-to-have This label is used by an internal tool labels Oct 14, 2020 — with ASP.NET Core Issue Ranking
@javiercn javiercn added feature-blazor-server reevaluate We need to reevaluate the issue and make a decision about it labels Apr 19, 2021
@javiercn javiercn mentioned this issue Nov 5, 2021
Closed
@mkArtakMSFT mkArtakMSFT modified the milestones: Backlog, BlazorPlanning Nov 5, 2023
@ghost
Copy link

ghost commented Dec 29, 2023

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.

@mkArtakMSFT
Copy link
Member

Closing as this will be obsoleted by #35897

@mkArtakMSFT mkArtakMSFT closed this as not planned Won't fix, can't repro, duplicate, stale Jan 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
affected-most This issue impacts most of the customers area-blazor Includes: Blazor, Razor Components enhancement This issue represents an ask for new feature or an enhancement to an existing one feature-blazor-server Pillar: Technical Debt reevaluate We need to reevaluate the issue and make a decision about it severity-nice-to-have This label is used by an internal tool
Projects
None yet
Milestone
.NET 9 Planning
Development

No branches or pull requests
3 participants
@SteveSandersonMS @javiercn @mkArtakMSFT