Gorgo.Live.ToString()

Mariusz, Gorzoch tech Blog

A word around SharePoint performance

leave a comment »

Few days ago my boss asked me to take a look at our intranet portal and check if I can do something around it performance. I started to dig around and found few tips, which can be done to improve SharePoint performance (especialy for Pubishing sites) without changin a single line of code (this was quite importent for my as unfortunetly do not have yet a good backup plan for our intranet enviroment). Below you can find a short description what to do and a link, when you can read more about it:
 
1. Enable output caching.
This is quite silly that this is not turn-on by default. If you are working with publishing site, you deffinietly should go and turn this option on. This tell the sharepoint that he can add special headers to his response to let users browser to cache some data on they site. In addition SharePoint will try to cache some sites on his site, which should also improve performance (this will force caching results of ASPX processing).
You can read more about this here : http://msdn.microsoft.com/en-us/library/aa661294.aspx
 
2. Enable object caching
Object caching let SharePoint to precache some heavly used object/items and reuse them for some period of time. This speed up entire sharepoint as he don’t have to create those object from scraches. In general this reduces trafic betwean front-end server and SQL database.
 
3. Enable IIS compression
When you use some tracking tool like Fiddler, you can find, that SharePoint send much more to the end user, then just a pure site. This entire content is text based and in case of use some compression can be packed quite good. To do this, we can use build-in functionality of IIS, which let us compress the output content before sending it to the end user. To do this, we just need to call 4 commands and check one box in IIS configuration.
If you go for that, you need to be aware that enablig this functionality on the farm will take a while. In my case compression started to work at around 1-2 hours after I did turn it on. I don’t know what is the reason for that, but it is good to know this, before you destroy you metabase.xml file of IIS, ;).
 
4. Enable blob caching
Blob caching tells the SharePoint to cache some static files, wich are hold in SQL database and query by SharePoint. Those files are CSS, JS, GIF, JPG, and so on. In an nutshell every file which is stored in database and could be stored in file system. If you enable this option, then you will limit amount of round trips betwean front-end and SQL and by this improve performance of the entire farm.
 
5. Enable anonymouse access
In publishing scenerios we can find a lot of content which can be exposed with anonymouse rights. Grouping this content togheter and exposing it with pure anonymouse rights will also improeve performance, as sharepoint will not have to authenticate user for each request. In addition output caching can cache those items in file system and improve response time.
 
Ok, that is all I found. I like those tips as they can help you improve performance without any risky deployment or changing your already deployed solution.
 
addintional resources:
Advertisements

Written by Mariusz Gorzoch

1 July 2009 at 22:04

Posted in SharePoint

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: