Hi Rocmad Sigit,
When your application is first accessed either after it was deployed, or if it has been idle for the timeout period, then the web server mus start the worker process an depending on some settings in your web.config, extract resources and icons etc.
There are a few things that you can do to minimize the time. Note however that the first time you access your application after you deploy it, it will take more time than the suceeding accesses, but that should not be huge problem because you can make it a part of your deploy procedure to access the application to make sure everything is ok.
Please view the Wiki Configuration page for details on how to change each setting mentioned below:
- Static Resources Mode="On". See more info on the wiki page for what it does.
- Skins Preloading and Icons Preloading can be set to "On" also for the same functionality as for StaticResources.
- Disable Obscuring should be "0", meaning that Obscuring is enabled.
- Disable Caching should be "0", meaning that Caching is enabled.
On top of these Visual WebGui settings, you can also try to minimize the chance of the IIS Worker process needs restarting and that you can do by adjusting the timeout settings for the application pool in IIS, effectinvely keeping the process intact for longer periods of time before it shuts down.
Hope this helps,
Palli