Application Pool Recycling

All

We've got most of our larger workflows set up using Reference workflow activities now. This aims to stop delays in loading the large files. The first workflow is basically lightweight and just notifies the user that something's processing.

If the application pool has been started/stopped or recycled since the tool was last run, it takes a significant ammount longer than the next time. We assume that this is because the app pool is loading the workflow into memory. Correct?

Our app pool recycles by default every 29 hours, so roughly every day the first users of the tools are faced by these delays. Is there any way of intitiating the workflows by script or something of that nature so that the workflows are 'initiated' prior to the user hitting them?

Thanks,

James