G
Guest
Hi
When ASP.NET site has been idle for a period of time, the workerprcess, caching, recycling have involved to make it taking 30-40 seconds to load the intial page. I have tried unchecking "Shutdown worker process..." and unchecking "Recycle worker processes..." but it still does not change anything. One thing I know is after the site being activated, the rest of it is as fast as it should be. Therefore instead of trying the above in vain, I am thinking to let the site being activated periodically to keep the site always active. So the users need not wait 30-40 seconds to load the first page when he is the first one visiting the site when it is idle for a while.
I know the system has a ScheduleTask which can kick off an application as scheduled. My question is how would I utilize this utility or is there anything available that can do what I want
When ASP.NET site has been idle for a period of time, the workerprcess, caching, recycling have involved to make it taking 30-40 seconds to load the intial page. I have tried unchecking "Shutdown worker process..." and unchecking "Recycle worker processes..." but it still does not change anything. One thing I know is after the site being activated, the rest of it is as fast as it should be. Therefore instead of trying the above in vain, I am thinking to let the site being activated periodically to keep the site always active. So the users need not wait 30-40 seconds to load the first page when he is the first one visiting the site when it is idle for a while.
I know the system has a ScheduleTask which can kick off an application as scheduled. My question is how would I utilize this utility or is there anything available that can do what I want