Windows 10: Announcing .NET 5.0 Preview 7

Brink · Jul 23, 2020

Today, weâre releasing .NET 5.0 Preview 7. Itâs the second to last of the preview releases (before moving to RC). Most features should be very close to done at this point. Single file and ARM64 intrinsics are two feature areas that are taking the longest time to complete, but are on track for Preview 8. See the .NET 5.0 Preview 4 post for a broader view of the release.

ASP.NET Core and EF Core are also being released today.

You can download .NET 5.0 Preview 7, for Windows, macOS, and Linux:

Installers and binaries

Container images

Snap installer

Release notes

Known issues

GitHub issue tracker

You need to use Visual Studio 2019 16.7 to use .NET 5.0. .NET 5.0 is now supported with Visual Studio for Mac. Install the latest version of the C# extension to use .NET 5.0 with Visual Studio Code.

Performance

Stephen Toub recently posted his Performance Improvements in .NET 5 post, the latest in his series. He covers ~250 performance-oriented pull requests, which reveal improvements that will even surprise people who follow .NET Core performance closely.

System.Text.Json

Weâve been adding usability feature to the new JSON API. The following features are new in Preview 7 (more coming in Preview 8, too).

Breaking change - Ability to ignore default values for value-type properties when serializing â can be used to reduce serialization and wire costs.

Ability to handle circular references when serializing â API shape is now expected to be final.

Garbage Collection (GC)

The GC now exposes detailed information of the most recent collection, via the GC.GetGCMemoryInfo method, which returns a GCMemoryInfo struct. GCMemoryInfo provides information about machine memory, heap memory and the most recent collection, or most recent collection of the kind of GC you specify â ephemeral, full blocking or background GC.

The most likely use cases for using this new API are for logging/monitoring or to indicate to a loader balancer that a machine should be taken out of rotation to request a full GC. It could also be used to avoid container hard-limits by reducing the size of caches.

Another, small but impactful change, was made to defer the expensive reset memory operation to low-memory situations. We expect these changes in policy to lower the GC latency (and GC CPU usage in general).

RyuJIT

RyuJIT is the assembly code generator for .NET, target both Intel and ARM chips. Most of the investment in RyuJIT is focused on performance.

General Improvements

Enable eliding some bounds checks â Credit @nathan-moore

Optimize Enum.CompareTo after being rewritten in C# â performance is now at parity with previous C++ implementation.

Improvement in register allocation for structs â Enregister multireg lclVars

Improvements for removal of redundant zero inits

Tail duplication improvement

Stack based structs copy CQ fix

Clean up a dead field assignment after removing redundant zero initializations

ARM64 hardware intrinsics & API optimization

Implement majority of âby elementâ intrinsics

Implement fcvtxn, fcvtxn2, sqabs, sqneg, suqadd, usqadd intrinsics â #38010, #38110

Optimize SpanHelpers.IndexOf(byte), SpanHelpers.IndexOf(char)

Optimize SpanHelpers.IndexOfAny(byte)

Optimize WithLower, WithUpper, Create, AsInt64, AsUInt64, AsDouble

Optimize AsVector, AsVector128, GetUpper, As and WithElement

Closing

Please tell us about your experience using Preview 7. Itâs not too late to share your feedback. We are getting close to the end of the release, but are actually more focused on quality now since we are largely done with feature development.

After Preview 8, we plan to release two RCs before the final release. The RCs will have âgo liveâ licenses, meaning theyâll be supported in production. On that note, weâve been running the dot.net site on .NET 5.0 since Preview 1 (50% on 5.0; 50% on 3.1) and it has worked great.

Richard Lander,
Program Manager, .NET Team
Click to expand...

Source: https://devblogs.microsoft.com/dotne...5-0-preview-7/

Tweet

— Twitter API (@user) View on Twitter
Click to expand...

:)

Brink · Jul 31, 2020

Announcing .NET 5.0 Preview 7

Today, we’re releasing .NET 5.0 Preview 7. It’s the second to last of the preview releases (before moving to RC). Most features should be very close to done at this point. Single file and ARM64 intrinsics are two feature areas that are taking the longest time to complete, but are on track for Preview 8. See the .NET 5.0 Preview 4 post for a broader view of the release.

ASP.NET Core and EF Core are also being released today.

You can download .NET 5.0 Preview 7, for Windows, macOS, and Linux:

Installers and binaries

Container images

Snap installer

Release notes

Known issues

GitHub issue tracker

You need to use Visual Studio 2019 16.7 to use .NET 5.0. .NET 5.0 is now supported with Visual Studio for Mac. Install the latest version of the C# extension to use .NET 5.0 with Visual Studio Code.

Performance

Stephen Toub recently posted his Performance Improvements in .NET 5 post, the latest in his series. He covers ~250 performance-oriented pull requests, which reveal improvements that will even surprise people who follow .NET Core performance closely.

System.Text.Json

We’ve been adding usability feature to the new JSON API. The following features are new in Preview 7 (more coming in Preview 8, too).

Breaking change - Ability to ignore default values for value-type properties when serializing — can be used to reduce serialization and wire costs.

Ability to handle circular references when serializing — API shape is now expected to be final.

Garbage Collection (GC)

The GC now exposes detailed information of the most recent collection, via the GC.GetGCMemoryInfo method, which returns a GCMemoryInfo struct. GCMemoryInfo provides information about machine memory, heap memory and the most recent collection, or most recent collection of the kind of GC you specify – ephemeral, full blocking or background GC.

The most likely use cases for using this new API are for logging/monitoring or to indicate to a loader balancer that a machine should be taken out of rotation to request a full GC. It could also be used to avoid container hard-limits by reducing the size of caches.

Another, small but impactful change, was made to defer the expensive reset memory operation to low-memory situations. We expect these changes in policy to lower the GC latency (and GC CPU usage in general).

RyuJIT

RyuJIT is the assembly code generator for .NET, target both Intel and ARM chips. Most of the investment in RyuJIT is focused on performance.

General Improvements

Enable eliding some bounds checks — Credit @nathan-moore

Optimize Enum.CompareTo after being rewritten in C# — performance is now at parity with previous C++ implementation.

Improvement in register allocation for structs — Enregister multireg lclVars

Improvements for removal of redundant zero inits

Tail duplication improvement

Stack based structs copy CQ fix

Clean up a dead field assignment after removing redundant zero initializations

ARM64 hardware intrinsics & API optimization

Implement majority of “by element” intrinsics

Implement fcvtxn, fcvtxn2, sqabs, sqneg, suqadd, usqadd intrinsics — #38010, #38110

Optimize SpanHelpers.IndexOf(byte), SpanHelpers.IndexOf(char)

Optimize SpanHelpers.IndexOfAny(byte)

Optimize WithLower, WithUpper, Create, AsInt64, AsUInt64, AsDouble

Optimize AsVector, AsVector128, GetUpper, As and WithElement

Closing

Please tell us about your experience using Preview 7. It’s not too late to share your feedback. We are getting close to the end of the release, but are actually more focused on quality now since we are largely done with feature development.

After Preview 8, we plan to release two RCs before the final release. The RCs will have “go live” licenses, meaning they’ll be supported in production. On that note, we’ve been running the dot.net site on .NET 5.0 since Preview 1 (50% on 5.0; 50% on 3.1) and it has worked great.

Richard Lander,
Program Manager, .NET Team
Click to expand...

Source: https://devblogs.microsoft.com/dotne...5-0-preview-7/

Tweet

— Twitter API (@user) View on Twitter
Click to expand...

Brink · Jul 31, 2020

Announcing .NET 5.0 Preview 2 now available

Today, we’re releasing .NET 5.0 Preview 2. It contains a set of smaller features and performance improvements. We’re continuing to work on the bigger features that will define the 5.0 release, some of which are starting to show up as initial designs at dotnet/designs. The .NET 5.0 Preview 1 post covers what we are planning on building for .NET 5.0. Please take a look at the post and the designs repository and share any feedback you have. And, of course, please install Preview 2, and test any workloads you can with it.

You can download .NET 5.0 Preview 2, for Windows, macOS, and Linux:

.NET 5.0 Preview 2 and Runtime

Docker images

Snap installer

ASP.NET Core and EF Core are also being released today.

You need to use Visual Studio 2019 16.6 to use .NET 5.0. Install the latest version of the C# extension, to use .NET 5.0 with Visual Studio Code. Visual Studio for Mac isn’t yet supported.

Release notes:

.NET 5.0 Preview 2 release notes

.NET 5.0 known issues

GitHub tracking issue

Let’s look at some of the improvements in Preview 2.

Code quality improvements in RyuJIT

Every release includes a set of changes that improve the machine code that the JIT generates (we call this “code quality”). Better code quality means better performance. In summary, about half of the following improvements are actual new optimizations and the other half are due to changing the flow of RyuJIT to enable existing optimizations to apply to more code patterns.

Use xmm for stack prolog – dotnet/runtime #32538 — Change to x86/x64 prolog zeroing code. Improvements: Json; TechEmpower. Credit: Ben Adams.

Add ValueNumbering support for GT_SIMD and GT_HWINTRINSIC tree nodes – dotnet/runtime #31834 — Enable the optimizer for SIMD and hardware intrinsic types.

Use GT_NULLCHECK for unconsumed indirections – dotnet/runtime #32641 — Remove redundant null checks.

invoke nullable box optimizations earlier – dotnet/runtime #32269 — Improve optimizations for Nullable<T>.

Optimize range checks for various array index patterns – dotnet/runtime #1644 — Improvement in range check elimination.

Optimize obj.GetType() != typeof(X) for sealed classes – dotnet/runtime #32790 — Improvement to type check expression.

Eliminate duplicate zero initializations more aggressively – dotnet/runtime #31960 — Better and broader approach for eliminating duplicate zero initializations.

Fix method and basic block flags used by early opts – dotnet/runtime #2196 – Enables certain optimization to be used more often. For example, replacing array length with a constant now occurs much more often.

If you like this style of improvement or are an ARM64 user, you may be interested in Vectorise BitArray for ARM64, coming soon (already merged, but not in Preview 2). This change demonstrates a lot of focus on ARM64 in .NET 5.0.

Garbage Collector

Card mark stealing – dotnet/coreclr #25986 — Server GC (on different threads) can now work-steal while marking gen0/1 objects held live by older generation objects. This means that ephemeral GC pauses are shorter for scenarios where some GC threads took much longer to mark than others.

Introducing Pinned Object Heap – dotnet/runtime #32283 — Implemented part of the POH (Pinned Object Heap) feature – the part internal to GC. This new heap (essentially a peer to LOH) will allow the GC to manage pinned objects separately, and as a result avoid the negative effects of pinned objects on the generational heaps.

Allow allocating large object from free list while background sweeping SOH – dotnet/runtime #2103 — Enabled LOH allocations using the free list while BGC is sweeping SOH. Previously this was only using end of segment space on LOH. This allowed for better heap usage.

Background GC suspension fixes – dotnet/coreclr #27729 — Suspension fixes to reduce time for both BGC and user threads to be suspended. This reduces the total time it takes to suspend managed threads before a GC can happen. dotnet/coreclr #27578 also contributes to the same outcome.

Fix named cgroup handling in docker – dotnet/runtime #980 — Added support to read limits from named cgroups. Previously we only read from the global one.

Closing

Please take a moment to try out Preview 2, possibly in a container, a VM. We’d like your feedback on the quality of the release. There is a lot more coming, over the next several months, leading up a November release.

We’re running 50% of the .NET Website traffic on .NET 5.0 as a test case, using Azure load balancing. We’ve been doing that since days after we released Preview 1. You may remember us doing something similar with .NET Core 3.0 and 3.1. By splitting the traffic 50/50, we can ensure that 5.0 gets consistently better with constant performance data available to us. This model keeps us honest, and it’s also a great testing approach. We trust our most important site with ALL of our previews, in production (which we don’t recommend for anyone else). That should make adopting our final release a pretty easy choice for you. The version number is in the footer of .NET website; feel free to check at any time.

Stepping back for a minute, many of you might be interested in how the the folks on the .NET Team at Microsoft are doing. We’re doing well. We have lots of Teams meeting every day to organize and support one another, and are just as active on GitHub as ever. The team is close-knit, and collaborating across multiple time-zones. We’re all focused on this release, and very much intending to deliver what we set out to deliver when we first defined our plans, after releasing .NET Core 3.0. Take care.

Richard Lander
Program Manager, .NET Team
Click to expand...

Source: https://devblogs.microsoft.com/dotne...5-0-preview-2/

See also: Regex Performance Improvements in .NET 5 | .NET Blog

Tweet

— Twitter API (@user) View on Twitter
Click to expand...

Brink · Jul 31, 2020

Announcing .NET 5.0 Preview 3 now available

Today, we’re releasing .NET 5.0 Preview 3. It contains a set of new features and performance improvements. We’re continuing to work on the bigger features that will define the 5.0 release. The .NET 5.0 Preview 1 post covers what we are planning on building for .NET 5.0. Please take a look at the post and the dotnet/designs repository and share any feedback you have. And, of course, please install Preview 3, and test your workloads with it.

You can download .NET 5.0 Preview 3, for Windows, macOS, and Linux:

.NET 5.0 Preview 3 and Runtime

Docker images

Snap installer

ASP.NET Core and EF Core are also being released today.

You need to use Visual Studio 2019 16.5 to use .NET 5.0. Install the latest version of the C# extension, to use .NET 5.0 with Visual Studio Code. .NET 5.0 isn’t yet supported with Visual Studio for Mac.

Release notes:

.NET 5.0 Preview 3 release notes

.NET 5.0 known issues

GitHub tracking issue

Let’s look at some of the improvements in Preview 3.

Code quality improvements in RyuJIT

Every release includes a set of changes that improve the machine code that the JIT generates (we call this “code quality”). Better code quality means better application performance.

Vectorise BitArray for ARM64 – dotnet/runtime #33749 — The BitArray class was updated to include a hardware-accelerated implementation for ARM64 using ARM64 intrinisics. The performance improvements for BitArray are very significant. Credit to @Gnbrkm41.

Implement simple version of On Stack Replacement (OSR) – dotnet/runtime #32969. On-stack replacement (OSR) is a new capability that allows the code executed by currently running methods to be changed in the middle of method execution, while those methods are active “on stack”. This feature is currently experimental and opt-in (on x64), and targeted at improving the more challenging performance characteristics of tiered compilation. Please try it out and give us feedback.

Dynamic generic dictionary expansion feature dotnet/runtime #32270 – Some (maybe many) uses of generics now have better performance (initial performance findings), based on improving the implementation of low-level (native code) dictionaries used by the runtime to store information about generic types and methods. See Perf: Collection Count() is Slower in Core than the CLR for more information. Credit to @RealDotNetDavefor the bug report.

Implement Vector.Ceiling / Vector.Floor dotnet/runtime #31993 – Implement Vector.Ceiling / Vector.Floor using x64 and ARM64 intrinsics, per API proposal. Credit to @Gnbrkm41.

JIT: allow CORINFO_HELP_READYTORUN_GENERIC_HANDLE to be optimized dotnet/runtime #34221. Improves code quality for generics in Ready2Run images.

JIT: enable tail calls and copy omission for implicit byref structs #33004. Improves code quality for structs as arguments in “tail call” position calls.

System.Text.Json improvements

Add support for preserve references on JSON dotnet/runtime #655 – Enables ReferenceLoopHandling, which is one of the key features of JSON.NET serialization.

Add new System.Net.Http.Json project/namespace dotnet/runtime #33459 – Adds new extension methods for HttpClient that allow serialization from/to JSON.

Add JsonConstructor and support for deserializing with parameterized ctors dotnet/runtime #33444 — Adds support for immutable classes and structs to JsonSerializer.

Add JsonIgnoreCondition & per-property ignore logic #34049 – Adds support for null value handling, which is another feature of JSON.NET serialization.

.NET SDK Support for .NET Framework Assemblies

The .NET SDK will now auto-reference the Microsoft.NETFramework.ReferenceAssemblies NuGet package given a .NET Framework target framework in a project file. This change enables building .NET Framework projects on a machine without the required .NET Framework targeting pack installed. This improvement is specific to targeting packs, and doesn’t account for other dependencies that a project may have.

Closing

Please take a moment to try out Preview 3, possibly in a container, a VM. We’d like your feedback on the quality of the release. There is a lot more coming, over the next several months, leading up a November release.

Richard Lander
Program Manager, .NET Team
Click to expand...

Source: https://devblogs.microsoft.com/dotne...5-0-preview-3/

Tweet

— Twitter API (@user) View on Twitter
Click to expand...

Windows 10: Announcing .NET 5.0 Preview 7

Announcing .NET 5.0 Preview 7

Announcing .NET 5.0 Preview 7

Announcing .NET 5.0 Preview 7

Announcing .NET 5.0 Preview 7 - Similar Threads - Announcing NET Preview

Announcing .NET 6 Preview 6

Announcing .NET 6 Preview 3

Announcing .NET 6 Preview 1

Announcing .NET 5.0 Preview 8

Announcing .NET 5 Preview 4 and our journey to one .NET

Announcing .NET 5.0 Preview 1

Announcing .NET Core 3.0 Preview 7

Announcing .NET Core 3.0 Preview 5

Announcing the .NET Framework 4.6.2 Preview