IIS appConcurrentRequestLimit

forbzie22_0253

Hi,

Does ProGet have a recommended limit on the max number of connections for appConcurrentRequestLimit setting in IIS?

It's 5000 by default but does increasing this to 10000 sound reasonable if the server has enough resources ?

Wasn't sure if ProGet had any hard limits within its own service etc so thought I'd ask

Thanks

atripp

Hi @forbzie22_0253 ,

We do not recommend modifying this value from the defaults; in fact, we recommend you avoid using IIS altogether.

IIS works poorly with modern .NET applications and tweaking settings will make it worse. For example, if you change "Max Worker Processes" to a value other than 1 (the default) you will likely get performance problems, since modern .NET are already multi-threaded and they will "compete" with each other.

ProGet has a built-in traffic queue that you can tweak under Admin > HTTP Settings > Web Server > edit. If you are having performance problems, then set it to 100 or so.

Cheers,
Alana

forbzie22_0253

@atripp Hi, I do plan on migrating over to Kestrel and Postgres but for the moment was looking to optimise IIS.
I could not find anything in the ProGet documentation to suggest you should not increase the limit higher than 5000, is your recommendation to not increase this number based off bad experiences with other customers ? Or are you just saying that the preferred approach is to use Kestrel?

Thanks

atripp

Hi @forbzie22_0253 ,

We have never seen a case where changing an IIS setting has benefited performance in any way whatsoever; instead we have only found headaches and problems from users modifying them. Those settings are not designed for modern .NET applications, but for like .NET Framework, classic ASP, etc.

So please don't touch them :)

Thanks,
Alana