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

Throughput for Server workloads on ARM64 is comparable to x64 #70530

Closed
3 tasks done
Tracked by #69887
JulieLeeMSFT opened this issue Jun 9, 2022 · 2 comments
Closed
3 tasks done
Tracked by #69887

Throughput for Server workloads on ARM64 is comparable to x64 #70530

JulieLeeMSFT opened this issue Jun 9, 2022 · 2 comments
Assignees
@richlander @JulieLeeMSFT
Labels
arch-arm64 area-Meta Cost:XL Work that requires one engineer more than 4 weeks Epic Groups multiple user stories. Can be grouped under a theme. Priority:1 Work that is critical for the release, but we could probably ship without
Milestone
7.0.0

Comments

@JulieLeeMSFT
Copy link
Member

JulieLeeMSFT commented Jun 9, 2022 •
edited
Loading

Summary

The server workload is both the most stressful and the most economically important. We want .NET Arm64 to be competitive with .NET x64, there should be no significant penalty for teams to use .NET Arm64.

What does success look like (include a metric if possible)

0.8x or better performance on key metrics, as compared to x64 baselines.

User Stories under this Epic
@JulieLeeMSFT JulieLeeMSFT added Epic Groups multiple user stories. Can be grouped under a theme. Priority:1 Work that is critical for the release, but we could probably ship without Cost:XL Work that requires one engineer more than 4 weeks labels Jun 9, 2022
@JulieLeeMSFT JulieLeeMSFT added this to the 7.0.0 milestone Jun 9, 2022
@dotnet-issue-labeler
Copy link

I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.

@JulieLeeMSFT JulieLeeMSFT mentioned this issue Jun 9, 2022
Closed
7 tasks
@ghost
Copy link

ghost commented Jun 10, 2022

Tagging subscribers to this area: @dotnet/area-meta
See info in area-owners.md if you want to be subscribed.

Issue Details

Summary

The server workload is both the most stressful and the most economically important. We want .NET Arm64 to be competitive with .NET x64, there should be no significant penalty for teams to use .NET Arm64.

What does success look like (include a metric if possible)

0.8x or better performance on key metrics, as compared to x64 baselines.

User Stories under this Epic

Author: JulieLeeMSFT
Assignees: richlander, JulieLeeMSFT
Labels:

Epic, area-Meta, Priority:1, Cost:XL
Milestone: 7.0.0

@jeffhandley jeffhandley modified the milestones: 7.0.0, Future Aug 11, 2022
@JulieLeeMSFT JulieLeeMSFT modified the milestones: Future, 7.0.0 Oct 14, 2022
@ghost ghost locked as resolved and limited conversation to collaborators Nov 13, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@richlander richlander

@JulieLeeMSFT JulieLeeMSFT

Labels
arch-arm64 area-Meta Cost:XL Work that requires one engineer more than 4 weeks Epic Groups multiple user stories. Can be grouped under a theme. Priority:1 Work that is critical for the release, but we could probably ship without
Projects
.NET Core CodeGen
Archived in project
Milestone
7.0.0
Development

No branches or pull requests
4 participants
@jeffhandley @richlander @jeffschwMSFT @JulieLeeMSFT