IIS on a Windows VPS hosts every website inside a worker process \u2014 and application pools are what keep those processes from destroying each other. Each site you add is assigned to a pool; when one pool’s worker process crashes or leaks memory, the other sites keep serving traffic. In practice, misconfigured application pools are the number one cause of 503 Service Unavailable errors, unexplained slowdowns, and middle-of-the-night restarts.<\/p>\n\n
You do not need a huge server to benefit from clean pool configuration, but you do need predictable resources. Compare Windows VPS plans on our comparison table<\/a> and make sure the RAM you choose matches the number of pools you plan to run \u2014 every worker process reserves memory before it ever serves a request.<\/p>\n\n Each pool maps to one or more In IIS Manager, right-click Application Pools<\/strong> and choose Add Application Pool<\/strong>. The same operation in PowerShell, using the built-in IISAdministration module:<\/p>\n\n Then assign the site to the pool: select the site \u2192 Basic Settings<\/strong> \u2192 choose the pool from the Application pool<\/strong> dropdown.<\/p>\n\n Two settings confuse everyone at first. .NET CLR Version<\/strong> should be Recycling restarts the worker process to clear leaked memory \u2014 but a badly timed recycle causes dropped sessions and cold-start delays. The defaults are a regular time interval of 1740 minutes (29 hours) and an idle time-out of 20 minutes. For production sites:<\/p>\n\n Recycle events are logged to the Application log with source If a worker process crashes five times in five minutes, rapid-fail protection stops the pool and every site in it returns 503. That behavior is correct for unhealthy apps, but for critical services raise the threshold or disable the stop action while you debug, and monitor the pool state:<\/p>\n\n By default a pool runs as If your application needs to read a network share or a database config file, switch the identity to a dedicated service account instead of handing out LocalSystem or Administrator rights \u2014 least privilege applies to worker processes too.<\/p>\n\n Set a Private Memory Limit<\/strong> (in KB) on the pool’s Recycling \u2192 Advanced Settings so a runaway process recycles instead of starving the VPS. A Web Garden<\/strong> (multiple worker processes per pool) spreads load across cores but breaks in-memory session state; only use it for stateless applications.<\/p>\n\n When a site hangs, restarting its pool is faster and safer than restarting the whole VPS. From an elevated PowerShell prompt:<\/p>\n\n You can script this into a health check: if a pool stays in the What an Application Pool Actually Is<\/h2>\n\n
w3wp.exe<\/code> worker processes. IIS routes requests for the sites in a pool to that process, and the process boundary is what contains crashes. One pool can host several sites, but then those sites share memory and recycling behavior \u2014 which is why most administrators create one pool per site, or one per application when a single site runs multiple apps.<\/p>\n\nCreate a Pool per Site<\/h2>\n\n
Import-Module IISAdministration\nNew-IISAppPool -Name \"contoso\"\nSet-ItemProperty IIS:\\AppPools\\contoso -Name managedRuntimeVersion -Value \"v4.0\"<\/code><\/pre>\n\n.NET CLR Version and Pipeline Mode<\/h2>\n\n
v4.0<\/code> for ASP.NET 4.x applications and No Managed Code<\/code> for static sites, PHP via FastCGI, or ASP.NET Core (which runs on its own in-process server). Managed Pipeline Mode<\/strong> should be Integrated<\/code> unless a legacy application explicitly requires Classic<\/code> \u2014 Integrated handles requests faster and supports modern modules.<\/p>\n\nRecycling: The Setting That Causes Most Outages<\/h2>\n\n
WAS<\/code>. Check the last few:<\/p>\n\nGet-WinEvent -LogName Application -MaxEvents 200 | Where-Object ProviderName -eq \"WAS\" | Select-Object -First 10 TimeCreated, Message<\/code><\/pre>\n\nRapid-Fail Protection<\/h2>\n\n
Get-ChildItem IIS:\\AppPools\\contoso | Select-Object State, ProcessModel<\/code><\/pre>\n\nApplication Pool Identity and File Permissions<\/h2>\n\n
ApplicationPoolIdentity<\/code> \u2014 a virtual account that must be granted explicit permissions on your content folders. Grant the site folder to the pool identity:<\/p>\n\nicacls C:\\inetpub\\wwwroot\\contoso \/grant \"IIS AppPool\\contoso:(CI)(OI)M\"<\/code><\/pre>\n\nMemory Limits and Web Gardens<\/h2>\n\n
Starting and Stopping Pools from the Command Line<\/h2>\n\n
Stop-WebAppPool -Name \"contoso\"\nStart-WebAppPool -Name \"contoso\"<\/code><\/pre>\n\nStopped<\/code> state after a crash, restart it automatically and send an event to the Application log so you notice the pattern before users do.<\/p>\n\nTroubleshooting Common Pool Failures<\/h2>\n\n