[ACCEPTED]-Application pool worker process Idle Time-out Action: Suspend vs Terminate-worker-process
I think you should choose
Terminate according 25 to your application environment.
Normally, to 24 configure Idle Worker Process Page-Out for 23 a Single Application Pool, we choose
Terminate, to 22 configure Idle Worker Process Page-Out as 21 a Default for Application Pools, we choose 20
IIS provides the administrator with an 19 option of timing out a worker process that 18 is idle for a specified period of time. This 17 is a good option for sites that are not 16 accessed very often because it frees up 15 system resources when the site is idle. The 14 disadvantage is that the next time the site 13 is accessed, the user will need to wait 12 for the worker process to start again.
Idle Time-out action, it provides an option of suspending an 10 idle worker process rather than terminating 9 it. A suspended worker process remains alive 8 but is paged-out to disk, reducing the system 7 resources it consumes. When a user accesses 6 the site again, the worker process wakes 5 up from suspension and is quickly available. When 4 an idle worker process is terminated, the 3 worker process is shut down and the startup 2 period will be longer when the site is subsequently 1 accessed.
I realize that this question is getting 13 "old" in internet time but I did 12 want to point out one thing. While I agree 11 with samwu and upvoted his answer, the OP 10 mentioned in the question and again in a 9 comment above that he wants to avoid potential 8 memory leaks. Suspend will NOT help with 7 that because the process is not terminated 6 so Windows cannot reclaim the "leaked" memory. "Suspend" is 5 to App Pools as "Hibernate" is 4 to your dekstop/laptop. If there is a problem 3 in/with memory and you Hibernate your computer, it 2 will still be there when you come out of 1 hibernation
More Related questions