{"id":29683,"date":"2020-09-02T09:50:12","date_gmt":"2020-09-02T16:50:12","guid":{"rendered":"https:\/\/devblogs.microsoft.com\/dotnet\/?p=29683"},"modified":"2021-09-29T12:15:46","modified_gmt":"2021-09-29T19:15:46","slug":"arm64-performance-in-net-5","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/dotnet\/arm64-performance-in-net-5\/","title":{"rendered":"ARM64 Performance in .NET 5"},"content":{"rendered":"

The .NET team has significantly improved performance with .NET 5, both generally and for ARM64. You can check out the general improvements in the excellent and detailed Performance Improvements in .NET 5<\/a> blog by Stephen. In this post, I will describe the performance improvements we made specifically for ARM64 and show the positive impact on the benchmarks we use. I will also share some of the additional opportunities for performance improvements that we have identified and plan to address in a future release.<\/p>\n

While we have been working on ARM64 support in RyuJIT for over five years, most of the work that was done was to ensure that we generate functionally correct ARM64 code. We spent very little time in evaluating the performance of the code RyuJIT produced for ARM64. As part of .NET 5, our focus was to perform investigation in this area and find out any obvious issues in RyuJIT that would improve the ARM64 code quality (CQ). Since Microsoft VC++ team already has support for Windows ARM64, we consulted with them to understand the CQ issues that they encountered when doing a similar exercise.<\/p>\n

Although fixing CQ issues is crucial, sometimes its impact might not be noticeable in an application. Hence, we also wanted to make observable improvements in the performance of .NET libraries to benefit .NET applications targeted for ARM64.<\/p>\n

Here is the outline I will use to describe our work for improving ARM64 performance on .NET 5:<\/p>\n