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.

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

.NET apps in containers have good startup and steady-state performance #5438

Closed
2 tasks
glennc opened this issue Oct 27, 2020 · 1 comment
Closed
2 tasks
Assignees
Labels
bulk-closed Priority:1 Work that is critical for the release, but we could probably ship without Team:Runtime User Story A single user-facing feature. Can be grouped under an epic.

Comments

@glennc
Copy link

glennc commented Oct 27, 2020

Take advantage of the immutable nature of container images and target modern hardware to produce more optimized assets.

  • Take advantage of modern SIMD instructions (AVX2 instead of SSE2) in ready-to-run images. We are comfortable with this because all containers are likely to be running on newer hardware and OS versions.
  • Use our Version Bubbles ideas to allow ready-to-run images to be more optimized, and as such more fragile to change. But the change is managed by the immutability of images.

Current Stories

  • Build composite image with Fx + asp.net Assemblies.
  • Enable composite Fx images for published container images
@jamshedd jamshedd added the User Story A single user-facing feature. Can be grouped under an epic. label Oct 28, 2020
@glennc glennc added the Priority:1 Work that is critical for the release, but we could probably ship without label Oct 28, 2020
@mairaw
Copy link
Contributor

mairaw commented May 26, 2023

Bulk closing .NET 6 epics and user stories. If you think this issue was closed in error, please reopen the issue and update it accordingly.

@mairaw mairaw closed this as completed May 26, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bulk-closed Priority:1 Work that is critical for the release, but we could probably ship without Team:Runtime User Story A single user-facing feature. Can be grouped under an epic.
Projects
None yet
Development

No branches or pull requests

6 participants