Hi all,
We've got an ASP Core application running behind an IIS proxy.
There's some confusion (disagreement) amongst us as to what the IIS configurations should be, and if they'll actually affect the performance of Kestrel. I was very much under the impression that the ASP Core application runs entirely outside of IIS, and therefore IIS configuration changes are largely unnecessary.
Some of us have spent a bit of time setting the maxconnections up in the web.config for IIS, and also the maxWorkerThreads etc. Is it right to assume that doing this will have no impact on the performance of the Kestrel server? We get very different results when we try to test this, so we're unsure as to what's going on.
Also, if this would not change Kestrel's behaviour, is there any reason to assume that the worker process for the ASP Core application would consume its request queue slower/faster depending on the IIS settings? Are there any gotchas that we should be aware of when setting up a reverse proxy?
Thanks!
Callum,