The first time you load up SharePoint, it is slow. If SharePoint only goes slow on the first load, this is because of JIT Compiling, but what can you do about it? The answer is very little because it’s designed behavior 😕 🙁
Basically, SharePoint’s pages are created dynamically from a combination of files on the server and data in the database. These dynamically created pages are compiled by the JIT (Just In Time) Compiler before they are served to the user. Once compiled, they are cached by the IIS Application pool.
Unfortunately, there is little you can do to stop SharePoint’s first load being slow, but here are a few things that can speed it up a bit:
- In SharePoint Central Admin, navigate to Manage Web Applications -> App – general and change Browserfilehandling to Permissive
- Run the following command on the SharePoint and SQL servers: netsh int tcp set global chimney=disabled
- Increase the connection time out (try doubling it)
- Clear the SharePoint Configuration Cache
- Restart IIS or the Application Pool
- Ensure that each SharePoint service is using it’s own AD account to run the service
You might also try disabling the JOT Compiler using the following command, but I have no idea what this will do to SharePoint:
To disable JIT compiling, run the following PowerShell commandlets on the SharePoint server:
Remove-ItemProperty -path “HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AeDebug” -name Debugger
Remove-ItemProperty -path HKLM:\SOFTWARE\Microsoft\.NETFramework -name DbgManagedDebugger
Remove-ItemProperty -path “HKLM:\SOFTWARE\Wow6432Node\Microsoft\Windows NT\CurrentVersion\AeDebug” -name Debugger
Remove-ItemProperty -path HKLM:\SOFTWARE\Wow6432Node\Microsoft\.NETFramework -name DbgManagedDebugger