Last post Oct 02, 2017 09:34 AM by AngelinaJolie
Sep 29, 2017 10:14 PM|Subtractive_|LINK
I have a question regarding running Kestrel behind IIS and concurrent connections. I set up IIS on my dev machine running Windows 10 Pro and threw some load testing on the application. When running a ASP.NET MVC5 application i fairly quickly get very high
response times and eventually the server stops responding.
However, when running a ASP.NET Core 2.0 application in IIS, I seem to be able to throw so many requests on the server that the bottle neck becomes my connection speed (100Mbit/s).
Since as I stated earlier, I'm running this on my dev. machine with Win 10 Pro, I should have the limit of around 10 concurrent connections right? So my question is, is this not applicable when running Kestrel behind IIS? Or am I getting the much better
results because Kestrel can handle the large amount of requests much more efficiently than if running a .NET MVC5 application?
Thanks in advance!
Sep 30, 2017 01:02 AM|maherjendoubi|LINK
The Kestrel web server has new features that make it more suitable as an Internet-facing server. A number of server constraint configuration options was added in the
KestrelServerOptions class's new Limits property. You can now add limits for the following:
For more information, see Kestrel web server implementation in ASP.NET Core.
Sep 30, 2017 08:21 AM|kashyapa|LINK
Benchmarks for ASP.NET Core is available on GitHub here: https://github.com/aspnet/benchmarks
The tests are run against Kestrel. So yes Kestrel can take the load now ... there have been major improvements in kestrel in the latest release.
hope this helps.
Oct 02, 2017 09:34 AM|AngelinaJolie|LINK
Or am I getting the much better results because Kestrel can handle the large amount of requests much more efficiently than if running a .NET MVC5 application?
Based on these data ,the answer is yes;