CODEWITHSUNDEEP
asp.net-core.net-coreasp.net-core-2.0
Mr.Wang from Next Door
Mr.Wang from Next Door

Reputation: 14780

Performance improvements from ASP.NET Core 2.1 for full .NET framework?

I have an existing project basing on ASP.NET Core 2.0 running on full .NET framework. Microsoft doc of my case is here. The application is using Kestrel with libuv to serve incoming connections.

Theoretically, how does ASP.NET Core 2.1 improve/demote the performance of my case?

My project is running on full .NET Framework 4.7.2. It seems to me it will not benefited by the Performance Improvements in .NET Core 2.1. Right?

Also ASP.NET Core 2.1 release note mentioned.

Managed sockets replace libuv as Kestrel's default transport.

Does that make a lot of difference to the app running on full .NET framework?

Upvotes: 2

Views: 1497

Answers (1)

poke
poke

Reputation: 387507

You are correct. Since you are running on the .NET Framework, you are not affected by the performance improvements that were made with .NET Core 2.1. While the changes there are general changes that will eventually reach the .NET Framework as well (at least partially), we simply aren’t there yet.

If you want the best performance, then you should use .NET Core, which will always be the runtime where the most improvements will be made and where improvements will happen first.

However, that does not mean that the .NET Framework is slow or anything. Countless applications have been built on the .NET Framework in the past and that includes lots of really performance-critical things as well. Even Stack Overflow currently runs on the .NET Framework. So just because .NET Core can be faster, that does not make the .NET Framework bad. It’s perfectly fine to run on the full framework.

That being said, ASP.NET Core 2.1 of course also includes changes that may affect the performance. While most of the announced speed improvements come from the .NET Core 2.1 changes, it wouldn’t be surprising if there are other changes that will also show noticeable improvements. The Sockets transport layer is one of those.

Regardless of performance improvements, you should upgrade from 2.0 to 2.1 anyway. .NET Core 2.0 and ASP.NET Core 2.0 will reach EOL on October 1st 2018. So by that time, you should have upgraded if you want support from Microsoft.

Upvotes: 1

Related Questions