Self Service & Analyst Portal - Community
Configuring Application Pool Recycling
Direct link to topic in this publication:
A slow page load time can indicate that the application pool has been recycled since the last time the portal was accessed. When a user accesses a page on the Cireson Portal for the first time after an application pool recycle, an application start event occurs which will pull the ServiceManagement database cache into the browser memory cache. Especially for large customer environments this process can take up to a few minutes. This is a one-time event that occurs after each application pool recycle. Further, for each page that is accessed for the first time after an application pool recycle, IIS will take a little longer to generate the page and store the resulting page in the IIS output caching. This needs to be done only once for each page.
Once the web site memory cache is populated and a page has been cached in the output cache, subsequent requests for that page should be fast. The application pool recycles every 29 hours by default, so users can experience this as a slow initial load on a near-daily frequency. Because the default is 29 hours it will occur at a different time each day, sometimes occurring during business hours. Also, administrators may be recycling more often, especially if they are working on configuring the portal for an initial deployment.
One thing that can be done to help address this is to adjust application pool recycling frequency/conditions. While Cireson does not recommend shutting off app pool recycling completely, it can be delayed to occur once every few days or during specific time windows. To do this, open IIS:
- Navigate to Application Pools.
- Right click on CiresonPortal.
- Select Recycling...
- Edit the Recycling conditions. The default setting is 1740 minutes (29 hours). Cireson recommends only having the app pool recycle automatically 1/day during non-business hours.