Hi all ! I'm wondering why my sharepoint services are so slow. Each time I connect to my website I have to wait someting like 15-20 seconds (after the first connexion, it works fine). Each time I create a subsite, it's at least 20 seconds I have to wait... Is this normal, or is there a way to speed up things ? Thanks ! Z. PS : It's not a hardware problem, hardware is far more sufficient in my case

I wouldn't call that "normal". I wouldn't call it unheard of either, particulary for a development environment running on a VM in a laptop. The first time you hit WSS after an iisrest or reboot or app pool recycle, the system will be "slow" as it caches a lot of stuff. Subsequent hits will be quicker. That seems to be what you described. 20 seconds to create a site seems like too long, but 5 to 10 seconds would not (to me, personally). After it's created, is it fast to access? I've seen properly sized and configured SharePoint environments run very quickly. It's not inherently slow. I think that the forum here can give you better input on addressing problems if you provide more details. HTH, --Paul Galvin, Conchango RSS @ http://feeds.feedburner.com/PaulGalvinsSharepointSpace Web site @ http://paulgalvin.spaces.live.com

Z. I posted a while ago on why SharePoint seems slow when you first use it http://www.21apps.com/2007/09/why-is-sharepoint-slow-when-i-first-use.html Also includes some tips on 'warming up' your sites. As Paul said please provide more details about specific speed issues like site collection creation etc and your configuration. Andrew

In my experience most slow downs in SharePoint 2007 are 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 Not sure if this will solve your problem, but it is worth looking into when you are experiencing slow spin-up times of the server or wheninvoking stsadm.

You seem to have a bug in your bonnet about this as you are posting about it everywhere, Jeroen. It's getting more than a bit boring. In this case the problem is clearly the initial load of ActiveX components that occurs the first time a site is opened in a new copy of the browser. It's avoided by using a browser that doesn't support ActiveX like Firefox.

It does indeed bug me. It has been a major pain in quite a few of the SharePoint deployments I have seen and worked with. As far as I am concerned it is agreat time saver so as a service to the community I searched for other people who were suffering from slow performance and replied to their postings. All in relevant threads. I am sorry if this bores you, but the way you see and use these forums is probably different from the average user. But then maybe I am wrong, what do I know.

I found the following solution on Jeroen's site which fixed the problem for me and was very easy to implement just involved editing the aspnet.config file with one line, http://msdn.microsoft.com/en-us/library/bb629393.aspx. Sharepoint now loads really fast < 10 seconds.

I just want to say Germel's fix had a dramatic effect on our Sharepoint performance. We went from about 10 seconds to load a word doc to under 2. We are running Sharepoint 2010 on Server 2008 R2 and I just went to c:\windows\microsoft.net\framework\v4.0.30319 and c:\windows\microsoft.net\framework64\v4.0.30319 and added the following line to aspnet.config, directly under runtime : <generatePublisherEvidence enabled="false"/> . What a difference! Thanks Germel!

Thanks for providing more detailed instructions ramtech65. This seem to do the trick.

I am having the same slowness issue. Is it applicable for .net 3.5 in win2008 R2? Please advice.vallaman