Performance Improvements in .NET 6

#1

Post by pjmlp » Wed, Aug 18, 2021, 6:12 AM UTC

Performance Improvements in .NET 6
devblogs.microsoft.com

Re: Performance Improvements in .NET 6

#2

Post by zigzag312 » Wed, Aug 18, 2021, 8:55 AM UTC

Some very nice improvements! I hope that this trend with focus on performance continues in the future and that NativeAOT becomes first class citizen soon.

Re: Performance Improvements in .NET 6

#3

Post by pjmlp » Wed, Aug 18, 2021, 10:14 AM UTC

zigzag312 wrote: post #2

Some very nice improvements! I hope that this trend with focus on performance continues in the future and that NativeAOT becomes first class citizen soon.

Becomes again, Native AOT is the only way on WinRT since Windows 8, but has been stuck in C# 7 and .NET Standard 2.0, which contributes even more for the little love UWP still has.

Re: Performance Improvements in .NET 6

#4

Post by azibi » Wed, Aug 18, 2021, 1:09 PM UTC

Impressive work (and blog post)! Somebody noticing real world performance impact after upgrading to latest .NET Core versions?

Re: Performance Improvements in .NET 6

#5

Post by vp8989 » Fri, Aug 20, 2021, 2:03 AM UTC

Making JIT 4% (or whatever) faster is cool but it would probably have higher ROI for the .NET ecosystem if Microsoft assigned some of these high caliber people to instead work on improving or simply rewriting some of the atrocious open source libraries that are available.

Would you rather have an A language/runtime with a D open source ecosystem or a B for both?

Re: Performance Improvements in .NET 6

#6

Post by ComputerGuru » Fri, Aug 20, 2021, 2:04 AM UTC

It’s an amazing write up. I posted this yesterday but it only had a few votes - I’m so glad to see it get attention. It’s a treasure trove of historical info, benchmarks, introspection into Win32 and .NET design decisions, and architectural trade-offs. It took me a long time to read through it, but I wonder how long it took Stephen to write.

Re: Performance Improvements in .NET 6

#7

Post by ComputerGuru » Fri, Aug 20, 2021, 2:07 AM UTC

pjmlp wrote: post #3

zigzag312 wrote: post #2

Some very nice improvements! I hope that this trend with focus on performance continues in the future and that NativeAOT becomes first class citizen soon.

Becomes again, Native AOT is the only way on WinRT since Windows 8, but has been stuck in C# 7 and .NET Standard 2.0, which contributes even more for the little love UWP still has.

Not just stuck - it was buggy and poorly maintained. We were forced to switch to Desktop Bridge after dealing with all the UWP performance and productivity crap and constraints just to have .NET Native one day stop compiling things right and leaving us stuck.

Re: Performance Improvements in .NET 6

#8

Post by MikeTheGreat » Fri, Aug 20, 2021, 2:08 AM UTC

vp8989 wrote: post #5

Making JIT 4% (or whatever) faster is cool but it would probably have higher ROI for the .NET ecosystem if Microsoft assigned some of these high caliber people to instead work on improving or simply rewriting some of the atrocious open source libraries that are available. Would you rather have an A language/runtime with a D open source ecosystem or a B for both?

I think that you're making a good point, and at the same time I think that tasking MS Devs with rewriting parts of their ecosystem is a bit of a minefield for any company, but especially Microsoft.

Long-term they need people to make good contributions to the ecosystem and I imagine it would be hard for third parties to sustain interest if it was a known risk that MS would rewrite whatever they were contributing.

I think you're spot on about the ecosystem being as important (or even more important?) than the core technology, and I'd love to hear peoples' thoughts on how to encourage such an ecosystem.

Re: Performance Improvements in .NET 6

#9

Post by kumarvvr » Fri, Aug 20, 2021, 2:11 AM UTC

For large enterprises, that use AWS / GCE / Azure, these improvements directly translate into huge savings in server capacity.

I have always loved .NET and it keeps getting better and better.

They have shown remarkable flexibility to throw away ideas that don't work and have modernized.

A large part of that is due to active involvement of the community.

This could be a new model moving forwards, a software worlds equivalent of "the customer is always right".

Re: Performance Improvements in .NET 6

#10

Post by throwaway13337 » Fri, Aug 20, 2021, 2:12 AM UTC

My favorite part of dotnet 6 is the focus on hot reloading not mentioned here.

Being able to work on a webapp that rapidly reloads in under a second is huge. It allows me to maintain the state of flow as I'm bringing something to life.

I had a unique use case wherein I had a separate worker thread that also needed reloading with the hotreload. I was able to hook into the hot reloading via "[assembly: System.Reflection.Metadata.MetadataUpdateHandler(typeof(MyHotreloadClass))]" and quickly solve my issue. I was pretty surprised to be able to modify that so easily.

The focus on performance and programming ergonomic makes me optimistic about the future of the platform. As someone who deploys to linux and is generally way outside of MS' ecosystem, this seems like a pretty big deal.