deersuper
asked on
what are the disadvantages of running multiple worker process thread in IIS 6.0.
what are the disadvantages of running multiple worker process thread in IIS 6.0.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Pretty much. Each one runs as a seperate application (controlled by IIS), so can place an inordinate overhead on your system if not carefully managed and planned.
Hi,
In addition, these worker processes run in isolation mode, which gives each application its own isolated memory segment. With this memory isolation, advanced administrators can limit an application's CPU utilization to get the maximum utility from a given server.
Multiple processes can be configured to service requests for individual application pools. By default each application pool has only one worker process but can be configured to support x number of processes. This is referred to as a Web garden because it is similar in nature to a Web farm, but the difference being that it is localized to one single server. The worker processes respond to requests in round-robin fashion. The benefit comes from having multiple worker processes being able to process requests even if an application service (such as the scripting engine) becomes unresponsive. Tying a particular process to a specific CPU is also available as an option.
http://www.15seconds.com/issue/030418.htm
http://technet2.microsoft.com/WindowsServer/en/library/b071455d-8ecf-4bae-ad46-ff61139ba87c1033.mspx?mfr=true
R.K
In addition, these worker processes run in isolation mode, which gives each application its own isolated memory segment. With this memory isolation, advanced administrators can limit an application's CPU utilization to get the maximum utility from a given server.
Multiple processes can be configured to service requests for individual application pools. By default each application pool has only one worker process but can be configured to support x number of processes. This is referred to as a Web garden because it is similar in nature to a Web farm, but the difference being that it is localized to one single server. The worker processes respond to requests in round-robin fashion. The benefit comes from having multiple worker processes being able to process requests even if an application service (such as the scripting engine) becomes unresponsive. Tying a particular process to a specific CPU is also available as an option.
http://www.15seconds.com/issue/030418.htm
http://technet2.microsoft.com/WindowsServer/en/library/b071455d-8ecf-4bae-ad46-ff61139ba87c1033.mspx?mfr=true
R.K
ASKER
makes sense !