Performance Improvements in .NET Core
blogs.msdn.microsoft.com
Performance Improvements in .NET Core
1–10 of 94 posts
Re: Performance Improvements in .NET Core
#2I hope most or all these will find their way into the full framework. It's a bit odd that this is so rarely mentioned. I still haven't quite grasped the relation between core and the full framework when it comes to fixes like this being merged into the full framework.
Re: Performance Improvements in .NET Core
#3> This is another great example of a developer caring a lot about a particular area of .NET and helping to make it better for their own needs and for everyone else that might be using it.
This is a great, succinct, non-ideological explanation for why open-source projects where anyone can contribute tend to be better. For a given component/function, there might be only a single person in the entire world who needs that optimized badly enough to actually do it themselves, but once they do, everyone benefits. A closed-source team has to prioritize their development efforts, which means niche improvements will probably never make it in. Multiply this by a thousand different niches, and the product is going to be slower.
Re: Performance Improvements in .NET Core
#4I hope most or all these will find their way into the full framework. It's a bit odd that this is so rarely mentioned. I still haven't quite grasped the relation between core and the full framework when it comes to fixes like this being merged into the full framework.
As .net core is a full rewrite, all these optimizations are .net core specific, so porting them isn't going to be a easy thing.
Re: Performance Improvements in .NET Core
#5I hope most or all these will find their way into the full framework. It's a bit odd that this is so rarely mentioned. I still haven't quite grasped the relation between core and the full framework when it comes to fixes like this being merged into the full framework.
From the post:
“We expect that many of these improvements will be brought to the .NET Framework over the next few releases, too”
We still need to ensure that all the changes are behavioral compatible. Other than that, we are intending on improving the .NET Framework as well with these same performance investments.
Re: Performance Improvements in .NET Core
#6I hope most or all these will find their way into the full framework. It's a bit odd that this is so rarely mentioned. I still haven't quite grasped the relation between core and the full framework when it comes to fixes like this being merged into the full framework.
As .net core is a full rewrite, all these optimizations are .net core specific, so porting them isn't going to be a easy thing.
Hopefully these optimizations are for a particular version of .NET Standard and will see themselves in both .NET Framework and .NET Core.
Re: Performance Improvements in .NET Core
#7I was expecting maybe 10% improvements, but many of these are 30x perf improvements on common collection operations
Re: Performance Improvements in .NET Core
#8Maybe at some point .net will be faster than Java.
Re: Performance Improvements in .NET Core
#9Earlier quoted context omitted.
As .net core is a full rewrite, all these optimizations are .net core specific, so porting them isn't going to be a easy thing.
Hopefully these optimizations are for a particular version of .NET Standard and will see themselves in both .NET Framework and .NET Core.
Skimming, but it doesn't look like these optimizations are relevant to .NET standard (which is a formal specification of a set of APIs - not a particular implementation.)
Re: Performance Improvements in .NET Core
#10Whenever I look at drastic improvements in performance, I remember that a while ago I managed to speed up a custom parser at work, by about 30x. When I emailed my colleagues, I just said "You may consider this to be work of a genius. Or you may think I was stupid when writing the original implementation. I'll let you pick the narrative that you fancy."
Interpretations are fun when there's a baseline :-)