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

Server-side Blazor perf infrastructure and hello world perf test #4052

Closed
danroth27 opened this issue Nov 16, 2018 · 4 comments
Closed

Server-side Blazor perf infrastructure and hello world perf test #4052

danroth27 opened this issue Nov 16, 2018 · 4 comments
Labels
affected-very-few This issue impacts very few customers area-blazor Includes: Blazor, Razor Components area-infrastructure Includes: MSBuild projects/targets, build scripts, CI, Installers and shared framework Components Big Rock This issue tracks a big effort which can span multiple issues feature-blazor-server ✔️ Resolution: Duplicate Resolved as a duplicate of another issue Perf Pillar: Technical Debt Priority:1 Work that is critical for the release, but we could probably ship without severity-nice-to-have This label is used by an internal tool Status: Resolved task
Milestone
.NET 9 Planning

Comments

@danroth27
Copy link
Member

No description provided.

@danroth27 danroth27 added task Perf area-mvc Includes: MVC, Actions and Controllers, Localization, CORS, most templates labels Nov 16, 2018
@danroth27 danroth27 added this to the 3.0.0-preview2 milestone Nov 16, 2018
@SteveSandersonMS SteveSandersonMS added the area-blazor Includes: Blazor, Razor Components label Feb 6, 2019
@mkArtakMSFT mkArtakMSFT assigned pranavkm and javiercn and unassigned javiercn Feb 6, 2019
@danroth27 danroth27 modified the milestones: 3.0.0-preview4, Backlog Feb 25, 2019
@rynowak rynowak added the Components Big Rock This issue tracks a big effort which can span multiple issues label Mar 4, 2019
@rynowak rynowak mentioned this issue Mar 4, 2019
Closed
56 tasks
@mkArtakMSFT mkArtakMSFT removed area-mvc Includes: MVC, Actions and Controllers, Localization, CORS, most templates labels May 9, 2019
@danroth27 danroth27 changed the title Razor Components perf infrastructure and hello world perf test Server-side Blazor perf infrastructure and hello world perf test May 22, 2019
@danroth27 danroth27 mentioned this issue May 22, 2019
Closed
11 tasks
@pranavkm pranavkm added affected-very-few This issue impacts very few customers severity-nice-to-have This label is used by an internal tool labels Oct 14, 2020
@mkArtakMSFT mkArtakMSFT modified the milestones: Backlog, 8.0-MQ Sep 30, 2022
@mkArtakMSFT mkArtakMSFT modified the milestones: 8.0-MQ, .NET 8 Planning Nov 21, 2022
@ghost
Copy link

ghost commented Nov 21, 2022

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.

@mkArtakMSFT mkArtakMSFT added triaged Priority:1 Work that is critical for the release, but we could probably ship without labels Nov 23, 2022
@amcasey amcasey added area-infrastructure Includes: MSBuild projects/targets, build scripts, CI, Installers and shared framework and removed feature-infrastructure-improvements labels Jun 1, 2023
@ghost
Copy link

ghost commented Oct 6, 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.

@ghost
Copy link

ghost commented Jan 3, 2024

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 in favor of #51971

@mkArtakMSFT mkArtakMSFT closed this as not planned Won't fix, can't repro, duplicate, stale Jan 3, 2024
@mkArtakMSFT mkArtakMSFT added the ✔️ Resolution: Duplicate Resolved as a duplicate of another issue label Jan 3, 2024
@ghost ghost added the Status: Resolved label Jan 3, 2024
@ghost ghost locked as resolved and limited conversation to collaborators Feb 7, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
affected-very-few This issue impacts very few customers area-blazor Includes: Blazor, Razor Components area-infrastructure Includes: MSBuild projects/targets, build scripts, CI, Installers and shared framework Components Big Rock This issue tracks a big effort which can span multiple issues feature-blazor-server ✔️ Resolution: Duplicate Resolved as a duplicate of another issue Perf Pillar: Technical Debt Priority:1 Work that is critical for the release, but we could probably ship without severity-nice-to-have This label is used by an internal tool Status: Resolved task
Projects
None yet
Milestone
.NET 9 Planning
Development

No branches or pull requests
7 participants
@pranavkm @SteveSandersonMS @rynowak @danroth27 @javiercn @amcasey @mkArtakMSFT