| <Update>SharePoint is very slowly the first time because it compiles all the libraries and after that they are cached. SharePoint is extremely slowly if this is done on a system which has no internet access because something else occurs during compilation! When I read the article about How to Optimize a SharePoint Server 2007 Web Content Management Site for Performance I stumbled upon a comment from Jeroen Ritmeijer who did some investigation upon the slow load times. Here is his comment and a link on what’s really going on: </Update> Ever since SharePoint 2007 was introduced I have been really disappointed with the 2 minute spin-up time of the sites and the 30 second wait when launching STSADM. As it turns out this problem does not occur on all SharePoint installations, it only happens under a certain combination of circumstances. Fortunately I have identified the root cause as well as a solution. Some symptoms: STSADM:
* You start STSADM without any parameters
* There is a delay of about 30 seconds
* There is no CPU activity, swapping or significant network traffic. SharePoint web requests
* You recycle the app pool / perform an IISRESET.
* Request a SharePoint page
* There is a delay of about 2 minutes
* There is no CPU activity, swapping or significant network traffic. After quite some investigation I have found that this is related to CRL (Certificate Revocation List) lookups when assemblies are being loaded. I have added a list of possible workarounds to the following blog posting: http://jritmeijer.spaces.live.com/blog/cns!8A48A27460FB898A!965.entry Thanks Jeroen ;) |