ARM64 - Prepare for the future

[jamshedd]

Theme: ARM64 - Prepare for the future

Objective

Enable customers to leverage ARM for better cost/power efficiency for cloud and client workloads without losing on performance or productivity.

Why

ARM64 brings parity performance with lower power consumption which makes it very attractive for lower COGS in server and cloud workloads. For Arm64 client, we are seeing increased performance and lower power usage compared to x64, completely changing the landscape for portable computing.

Customer Cohorts

Developers for server workloads currently running on x64

These customers are currently using x64 and would like to transition their workloads to use ARM64 server hardware to benefit from the COGS savings. These customers expect a similar level of performance and optimizations they’re used to on x64 today.

Developers currently using x64 to target ARM64 devices

These are developers that currently use x64 machines to build apps that will run on ARM64. Their dev inner loop experience is cumbersome since they have to develop and cross-compile for ARM64, then deploy to an external ARM64 device for local testing, and finally ship their app for ARM64.

X64 Client device users

These are customers that currently use x64 devices and could be convinced to buy an ARM64 device in the future if they were to get equivalent performance, longer battery life and lower cost with full compatibility for the apps they already use. These are consumers that would not want to accommodate differences in experience on account of using an ARM64 device instead of x64.

Ecosystem partners/library authors

While we are doing work to improve our own runtime and libraries there are a ton of third-party libraries that make up the .NET ecosystem and we want these to also be optimized for ARM64. Additionally there are also a large number of NuGet packages that shipped outside of mainstream .NET releases with unknown compatibility for ARM64 or even .NET Core.

Epics under this Theme:

• Developers can leverage Edit-and-Continue on Windows ARM64 #69907
• Throughput for Server workloads on ARM64 is comparable to x64 #70530
• Intrinsics parity with x64 for Arm64 #70533
• Top Microsoft and third party NuGet packages support and work well on ARM64 #70535
• Top used controls from the major control vendors work well on ARM64 #70536
• Arm64 improvements for Mono #70558
• ARM64 support for ASP.NET Core on IIS (ANCM) aspnetcore#39281

[ghost]

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

Issue Details

---

Theme: ARM64 - Prepare for the future

Objective

Enable customers to leverage ARM for better cost/power efficiency for cloud and client workloads without losing on performance or productivity.

Why

ARM64 brings parity performance with lower power consumption which makes it very attractive for lower COGS in server and cloud workloads. For Arm64 client, we are seeing increased performance and lower power usage compared to x64, completely changing the landscape for portable computing.

Customer Cohorts

Developers for server workloads currently running on x64

These customers are currently using x64 and would like to transition their workloads to use ARM64 server hardware to benefit from the COGS savings. These customers expect a similar level of performance and optimizations they’re used to on x64 today.

Developers currently using x64 to target ARM64 devices

These are developers that currently use x64 machines to build apps that will run on ARM64. Their dev inner loop experience is cumbersome since they have to develop and cross-compile for ARM64, then deploy to an external ARM64 device for local testing, and finally ship their app for ARM64.

X64 Client device users

These are customers that currently use x64 devices and could be convinced to buy an ARM64 device in the future if they were to get equivalent performance, longer battery life and lower cost with full compatibility for the apps they already use. These are consumers that would not want to accommodate differences in experience on account of using an ARM64 device instead of x64.

Ecosystem partners/library authors

While we are doing work to improve our own runtime and libraries there are a ton of third-party libraries that make up the .NET ecosystem and we want these to also be optimized for ARM64. Additionally there are also a large number of NuGet packages that shipped outside of mainstream .NET releases with unknown compatibility for ARM64 or even .NET Core.

Epics under this Theme:

Author:	jamshedd
Assignees:	jamshedd
Labels:	area-Meta, Theme
Milestone:	.NET 7.0

[jamshedd]

This has been moved to the runtime repo: #69887

[jamshedd]

Didn't mean to close this one :)