When we first access a Web site, the first hit takes longer as the server is loading all kind of stuff in memory. Then, on following hits, everything response immediately. On busy Web site, this is the scenario. So, usually, if we do an update, we do at least a few hits to make sure the startup initialization is done and that the other hits are processed immediately. But, for less busy servers, I have found that after a while, if no activity has been done on the server, that it will redo its initialization phase. I need to avoid that. Is there a setting in IIS to prevent that?