Application
pool
Application pools are used to separate sets of IIS worker
processes that share the same configuration and application boundaries.
Application pools used to isolate our web application for better
security, reliability, and availability and performance and keep running with
out impacting each
other.
Worker process
Generally, each Application Pool corresponds to one worker
process. A worker process is a windows process (w3wp.exe) which runs Web
Applications, and is responsible
for handling requests sent to a Web Server for a specific
application pool. The worker process serves as the process boundary that
separates each application pool so
that when one worker process or application is having an issue or
recycles, other applications or worker processes are not affected. One
Application Pool can have multiple worker process Also.
Main Point to Remember:
1. Isolation of Different Web Application
2. Individual worker process for different web application
3. More reliably web application
4. Better Performance
Application Pool Recycling
In case if we recycle the application pool then the worker process
of that pool will be restarted. We are recycling a application pool due to
application
crashes or hangs and to discontinue any irrelevant process with in
an application or memory leak.
By default IIS will use overlapped recycle method, When the worker
process terminates, a new one is started simultaneously. This type of recycling
is called
overlapped recycling.
Application Pool Recycling
Scheduling
Scheduling an application pool means i want to restart the worker
process at any specific time. How to schedule recycling an application is given
below image.
first go to Start->run->inetmgr it will open up IIS then
select your corresponding application pool where your application is running.
Now on right side of this window
you will find edit application pool as shown in the picture below.