collaboration portal performance issue

Question

I am using SharePoint Server 2007 on Windows Server 2008. I am using collaboration portal template. I experienced issues when loading the same page multiple times, the page loading time is almost the same. I think if there could be cache function, it should be better (e.g. the 1st time of loading is slow, but if the content could be cached. The if we load from the 2nd time, since it is cached, it will be very fast from end user perspective.).

I read from this document that seems collaboration portal has no read cache? Is that correct? Any ideas how to enable read cache of collaboration portal?

http://blogs.msdn.com/b/mossbiz/archive/2009/06/23/clarifications-collaboration-vs-publishing.aspx

BTW: here is the related content of the document I refer to which mentions collaboration portal has no cache,

Publishing needs heavy branding, high performance read-only access (caching), staging and deployment, while Collaboration needs clear functionality, ease of engagement, consistency between sites and high performance read/write access (no caching, fast servers).

thanks in advance, George

Answer 1

You need to setup object, output and blob cache for your site collection in relation to site usage. See my answer earlier on this subject:

SharePoint Web performance optimization

Publishing sites is usually web facing and allows anonymous access. This allows for a more agressive caching strategy, since site doesnt contain personalized items as a typical intranet does. In your typical collaboration site you need to take into account that content is personalized. If you cache those controls they will be shared amongst users. Hence you need a less agressive caching setting to avoid disclosing personal data across users.

Advanced scenarios in this area includes wrapping controls you dont want to cache with a substitution control, but this is a developer task and not simple to do.

About performance issues in general, make sure that you dont have alot of closed web parts on the page (add ?contents=1 to url). If your designers close web parts instead of deleting them this can severely affect performance.

Answer 2

Not sure if this is related to your particular performance problem, but you may be helped by reading this post I wrote some time ago: A new approach to solve SharePoint’s painfully slow spin-up / start-up time for first request.

Answer 3

Here are some techniques to Troubleshoot Page Loading Issues similar to Anders recommendation to check for closed web parts. http://nextconnect.blogspot.com/2010/01/troubleshooting-page-loading-issues.html