IIS application pool maximum number of processes setting

1, when the number of worker processes >1, if there are multiple connection requests will start multiple worker process instances to process, the maximum number of worker processes started is the maximum number of processes you set, subsequent more connection requests will be sent to different working processes to process. Each worker process can assume a load of some connection requests, at the expense of system resources such as cups.

2, each work process consumes system resources and CPU, too many worker processes will cause the system resources and CPU usage is consumed sharply; each worker process has its own state data, and if the Web application relies on a worker process to hold state data, setting up multiple worker processes will not work. If the number of worker processes set >1, the state data should use the StateServer or SQL Server storage format, instead of using the worker process (INPROC) mode, otherwise it will result in the log state information confusion-a user's request is processed by one of the worker processes, This is the logged in state; However, another request may be handled by a different worker process, which may be a non-logged-in state at this time;

IIS application pool maximum number of processes setting