Setting up max worker process and queue length for .net core web api

239 Views Asked by At

We are running performance run to test our .Net Core WEB API's. And, to have better results we have done below settings on IIS Server for WEB API's

QueueLength - 10000 MaxWorkProcess - 2 & 1 respectively (As we have hosted 2 different API projects into same IIS server and using same application pool.)

Above settings we have done on application pool. Our AWS EC2 instance has 4 vCPUs with 8 gb ram in place.

So, our question is do we need to setup this configuration for .net core api's? And, it is going made any different if we try to load concurrent users in the system?

Any help on this appreciated

0

There are 0 best solutions below