If there’s one thing that’s certain in SharePoint it’s growth. And as you SharePoint environment grows performance can become quite an issue. Obviously there are quite a few things that go into performance, however in this post I’d like to discuss three best practices or considerations.
Based on ASP.NET caching technologies, output caching can be configured for SharePoint 2010 allowing for potential performance improvements. Essential SharePoint 2010 will then cache the pages it outputs cutting down the need to generate a new page for every subsequent request. There are some benefits and drawbacks, see below.
- Less latency
- Lower CPU utilization
- Additional data source scalability
- Customizable output caching according to Cache Profiles
- Memory consumption
- Potential version inconsistency
Segregate Network Traffic
This isn’t necessarily a consideration, more of a best practice. Network bandwidth consumption is a huge concern for SharePoint and fortunately there’s a pretty simple way that you can optimize your network configuration for best performance, separate traffic. SharePoint places a great deal of demand on SQL and as such network traffic can be immense. In order to prevent any conflict between SQL and user traffic the SharePoint server should have a separate connection to front-end servers and a separate connection to the back-end database servers. This will allow for isolated communication meaning one source will not impact the other.
Another thing that you may want to consider is IIS compression. As with Output Caching there are benefits and drawbacks but essentially IIS compression will reduce the HTTP payload resulting in shorter load times. This however comes at CPU expense. As a default compression is enabled in IIS 7 but not configured. In order to configure run the following scripts in a command prompt.
%windir%\system32\inetsrv\appcmd.exe set config /section:httpCompression –[name=’gzip’].dynamicCompressionLevel:6
%windir%\system32\inetsrv\appcmd.exe set config /section:httpCompression –[name=’gzip’].staticCompressionLevel:6
These settings can be modified from 0 (no compression) to 10 (full compression). Higher values determine how aggressive IIS will be in employing the compression algorithm.
See here for additional information. (URL not valid anymore)
Performance in SharePoint is critical to providing an acceptable end-user experience. The items above are only a few of the many options an administrator has when optimizing their environments. I recommend additional reading for a more complete idea of what the options are, see here for a great arcticle. (URL not valid anymore)