Why does it take forever for SharePoint to load sometimes?
SharePoint is built on ASP.NET technology. Applications hosted through IIS, (like an ASP.NET website or SharePoint) must initially be compiled before being sent to the user. This is a process called Just-In-Time compilation. Application Pools within IIS are responsible for execution of applications (like SharePoint) they manage resources like memory, and invoke JIT compilation, as well as other services like caching. Applications Pools will naturally shut down if left idle as to free up resources no longer needed. Application Pools will also occasionally recycle or restart if memory thresholds are reached. In these cases, the Application Pool must initiate JIT compilation of hosted applications as well as begin allocating resources when a request for the application is received again. The user requesting the application for the first time will experience a delay while the Application Pool compiles the site and makes it available for servicing. Subsequent requests for the application do not occur this overhead. To prevent users from ever experiencing this delay, warm up jobs or scripts are created to request sites running on an IIS server periodically or before demand is expected. The initial delay in startup of an application pool still occurs, but the experience of a delay now occurs in a command prompt running as a scheduled task, not a user’s browser.
No Comments
Comments RSS
TrackBack Identifier URI
No comments. Be the first.
Leave a comment