Are you asking about the value for the application pool timeout?

I'm not really sure how well it works for long periods of time like that, it might be ok.

One thing you could do is keep a computer at home logged into your site with an edit page open like the html content editor. All our edit pages have a session keep alive feature enabled so it keeps making background requests to the site to prevent your session from timing out while editing content. Not the greatest solution but it does keep your app alive because even if the app is shut down the requests from the browser should start it right back up again.

Hope it helps,

Joe

Hi Andrew,

Well, it isn't completely true. IIS 7 is faster than IIS 6 but the JIT compile still takes place and that process is inherently slow. 

There are many other reasons to move to IIS 7+ and I think your site would benefit from them. Not to mention, it is always nicer to upgrade when it isn't a necessity. :-)

Thanks,
Joe D.

Your plan sounds exactly like what I would do.

Yes, moving a mojo SQLCE site is only a matter of moving the files and setting the proper permissions. Of course, you have to have .NET 4 on the new machine, but you know that. ;-)

HTH,
Joe D.

Just to give you a frame of reference, we are running Windows Server 2008 R2 (IIS 7.5) on a quad CPU Intel Xeon 5550 server with 16 GB of RAM. After app pool timeout, or making a change to the web.config file, our initial page load time is approximately 2.5 seconds.

Jamie

I'm not a fan of the AppKeepAlive task myself. I think using a free service like  UptimeRobot is a much better way to keep your site awake. Pingdom also can be used for free for 1 site.

I would disable the AppKeepAlive and use one of these.

It can help to ping more than just your home page, pinging pages that have different features on them is helpful to make sure everything is compiled.

It can also help to remove resx files for languages you are not using from the /App_GlobalResources folder and remove extra skins that you are not using.

Hope that helps,

Joe

Hi,

I supose that you are refering to the Idle Time-out(minutes) properti of the appPoool?

Yes, by default that is 20 minutes so after 20 minutes of no requests to your site IIS will shut down the app which means on the next request it has to compile again causing the slow initial startup again. The main reason for using something like uptimerobot or pingdom is to make sure it gets requests more frequently than the idle timeout to prevent the app from being shut down by IIS.  So setting the idle timeout to a much higher value would help a lot, then maybe no pinging service is needed to keep it awake, but it still wouldn't hurt since it will also shut down according to the Regular Time Interval.

Hope that helps,

Joe