We use our own .NET CMS for our sites and have been for several years. Up until maybe a month ago all sites loaded nice and fast. Lately, we've been noticing that if we haven't been to a site for a bit (say a day or even half a day), the first load can take 10 seconds or more just to get the first status 200 response from the server. Note this usually is the first load of any page on the site - subsequent page loads tend to be faster (though not always). So it does not seem to be on a page by page basis. The other day one was so bad (and it was the client that noticed) that Jodo moved it to it's a dedicated app pool. Since then, the site has been super fast every time I test it. This made me wonder if the insane server response time we've been noticing is related to the shared app pool or perhaps policies on recycling the app pools. Could someone help me understand what may be causing the extreme server response times (and maybe if this is related to the 503 Service Unavailable's we've gotten lately), and a bit about app pool practices and whether we can just request all sites have their own dedicated app pool? Thanks!