| Andy Stephens 2006-10-26, 7:15 am |
| Hi
We have the same issue. I believe it is simply down to both CMS and the
ASP.Net application initialising, CMS constructing its caches, and so on. The
first "hit" on a CMS application is more database-intensive as the node cache
has to be constructed from the database.
Just like any other ASP.Net application, this delay should only occur the
first time a user accesses a site after it has "restarted" for whatever
reason, e.g. after deploying a new version, changing web.config, restarting
IIS, or the IIS app pool has recycled, etc. (FYI if using IIS6, all the
recycling options should be switched off on the app pool where CMS runs).
Hope that helps
Andy
"Jan" wrote:
> Hello NG,
>
> I have a little problem. Whenever someone accesses a random cms application
> on the server (mcms 2002) for the first time, it takes up to 30 seconds to
> start the application. After that all other applications work fast without
> delay.
> looks like the server needs some time to wake up to come into operation mode?
> how can I fix this?
> after how many minutes of idle will the server switch back to sleep mode?
>
> I can reconstruct this behavior on 2 other mcms machines
>
> please help
>
> Jan
|