latest updates from easySERVICE™
Microsoft SharePoint is the fastest growing product in Microsoft history. Its adoption rate has been exponential with millions of documents being stored daily. With its growth critical documents and procedures are now being stored in SharePoint. It is fundamental that SharePoint maintains its healthy status, and application performance is a key component for a successful deployment and adoption of SharePoint.
These steps are there to help you with SharePoint performance to help organizations better understand the different ways and places SharePoint performance can be improved. SharePoint deployments are a combination of applications, services and databases where delivering a scalable, dynamic and efficient portal implementation can be a challenging task for even the most experienced IT professionals. Improvements can be made within or outside of the SharePoint infrastructure.
Step 7 Configure IIS Compression
SharePoint content consists of two primary sources—static files resident in the SharePoint root directories (C:\ Program Files\Common Files\Microsoft Shared\12 for 2007 and \14 for 2010) and dynamic data stored in the content database (web parts, publishing field controls, navigation controls, etc.). At runtime, SharePoint merges the page contents from both sources prior to transmitting them inside an HTTP response to the requesting user. Internet Information Server versions 6 (Windows Server 2003) and 7 (Windows Server 2008) both contain various mechanisms for reducing the payload of HTTP responses prior to transmitting them across the network. Adjusting these settings can reduce the size of the data transmitted to the client, resulting in shorter load times and faster page rendering. It is important to note that doing so can have an impact on CPU load and memory utilization – care should be taken to insure that sufficient hardware resources exist before tuning IIS compression settings.
IIS compression settings can be modified from a base value of 0 (no compression) to a maximum value of 10 (full compression). Adjusting this setting determines how aggressive IIS should be in executing the compression algorithms. Setting the value to 4 can result in a static linked file such as core.js being reduced in size from 79k to 60k, resulting in a payload reduction of 24%. Turning it up to 9 will reduce the size even further to 57k (it is generally recommended to avoid using the max setting of 10 as this can place excessive demands on the CPU). Environments which employ extensive custom branding and customization, and those with a large proportion of remote users on slower connections, will benefit the most from adjusting IIS compression levels.