Hi,

It can be done in server configuration. mojoPortal doesn't need to do a lot of expensive setup, so we really don't need to use the custom pre-load logic illustrated in the article.

Really the biggest problem is for low traffic sites where requests don't come in frequent enough and by default IIS will shut down the app after a period of no requests, then when a request finally comes in it needs to do all the JIT compiling again so the few users who visit get a slow site experience. Once the user clicks around a few pages all the JIT compiling is done and the site is much faster so a site that gets consistent traffic preforms much better. I'm not really sure the IIS warm up solves this problem, it seems to mainly be for large high traffic sites where there is a lot of setup needed when the app first starts.

In mojoPortal we have a low fi solution for the low traffic slow site problem where you can configure an AppKeepAlive task that starts a background thread that makes web requests to the site often enough to keep the timeout from happening so the site is not shut down by IIS.

Best,

Joe

Hi,

Yes, anything that forcefully recycles the app pool will kill the background thread as well. But when the app restarts after getting its next request the keep alive task will be started again from the Application_Start event.

The background task simply makes web request often enough to keep the timeout from happening that would cause IIS to shut down the app. ie it makes a web request on a frequency slightly shorter than the session timeout period so that there is always at least one active session.

Best,

Joe