Had le même question as le original poster mais could pas find a concise answer, ci-dessous is le analysis depuis mon research.
Application Pool != Worker Process (w3wp.exe)
- Typically we see a single w3wp.exe instance running for chaque application pool mais technically we can configure a web garden avec multiple w3wp.exe instances running.
Web gardens... are they good or bad or what?
- A worker process executes in le context of a single application pool.
Start application pool immediately = Automatic ou manual start
Basic Settings...
IIS will automatically démarrez le application pool.
Someone needs to manually démarrez le application pool.
Start Mode = Worker process start mode: immediately ou on demand
Advance Settings...
If le application pool is running immediately start up le w3wp.exe process.
If le application pool is running démarrez le w3wp.exe process quand there is an inbound application request.
Additional Notes
Stop IIS, application pool(s) et worker process(es) (w3wp.exe instances).
-
IISRESET /start
Start IIS et le ci-dessus configuration settings will determine quand le application pool(s) et worker process(es) (w3wp.exe) start up.
-
IIS Manager Stop Web Server GUI action
Arrêtez le web server depuis handling inbound requests mais will pas arrêtez le application pool(s) ou w3wp.exe process(es).
-
IIS Manager Start Web Server GUI action
Démarrez le web server to handle inbound requests mais will pas démarrez le application pool(s) ou w3wp.exe process(es).
Menu action to start/stop a Web Server
-
IIS Manager Stop Application Pool GUI action
Arrêtez le w3wp.exe process.
- IIS Manager Start Application Pool GUI action
AlwaysRunning vs. OnDemand will determined quand le w3wp.exe process starts up.
Menu action to start/stop an Application Pool
