I have a Windows 2003 server with .NET 1.1 sp1 installed. I have a web application that runs pre-compiled DLLs (these are aspx pages with the code-behinds in VB.NET DLLS). If I recompile a DLL, there's about a 10 -20 second delay opening the website. Then it serves up pages almost instaneously, as it should.
But if I don't visit the site for 20 minutes, then go back, the delay occurs again. I've done some research, and I think this is because the application pool the web app resides in has to launch a new w3wp.exe process every 20 minutes. I looked at the application pool properties, and I have 2 settings set as 20 minutes:
Recycle worker process: 20 minutes
Shutdown worker processes after being idle for 20 minutes.
Can I just increase the idle timeout to 1440 minutes (1 day)? Will that solve the problem, assuming someone visits the site once a day to keep the w3wp process running so it doesn't shutdown for an idle timeout.
Is there a better way, or does dot net just suck?