How to make use of application warm-up?

[djangodude Profile]

On the info page for Zoo, one of the features listed on http://www.helicontech.com/zoo/ is, "Application warm-up—don’t let your customers wait for a service."

I think this is something I want/need to take advantage of. What I'm seeing is: my application's worker will shut down after a period of inactivity (seems like about 20 minutes). Response to the initial request after the worker shut down takes a *long* time as the worker gets restarted, etc. I'd like to reduce that delay (prevent the worker shutdown?), and my guess is that some kind of "warm-up" is the way to do it.

Is there some guide for implementing application warm-up with Zoo?

[Yaroslav]

With default configuration application warm-up should be working fine. The problem is your current application worker shuts down for some reason. Helicon Zoo will not shut down last worker of the application, but worker can be recycled by IIS recycling policy or because application decided to exit for some reason (error trap or built-in recycling mechanism). You can check for IIS recycling options in IIS Application Pool settings. And make sure you are running latest version of Helicon Zoo Module and update it if possible.