[pullquote]I receive lots of comments and questions about performance recommendations for Microsoft SharePoint on a regular basis.[/pullquote]
I could be approached at conferences or even get asked for my advice in everyday conversations in the hallways or on the streets. In light of all the inquiries I have received thus far I decided to compile an short, easy to read list of recommendations for increasing performance for SharePoint that can be verbally related in as little as five minutes.
Decrease how many content database and site collections you use. I prefer the “accounting model” of managing databases over the “airline booking model.” If you know what the allowable maximum quota of site collections is, which is 5GB, and wish to contain your current databases at 100GB, you cannot host any more than 20 site collections on a single database. This can result in a significant amount of content databases, although avoid any huge increases in site collection.
When using this model, take into consideration the amount of growth your account will receive and put 5% to 10% aside for the support of changes in schema among other things. Keep your databases at a realistic size and the original size it was designed for. Microsoft SharePoint technologies and products will stipulate the content database at a certain number of MB and will be able to automatically provide account growth in 1MB increments. Having a miniscule number of site collections in a single content database will increase operations efficiency and can alleviate exposure to computer and database locking that may occur; this can happen to a smaller amount of users within the database more so than a larger population.
SharePoint Caching and Compression
Encourage BLOB caching, HTTP compression, and site output caching as deemed appropriate. When using an HTTP compression, you must monitor closely the processor utilization.
Windows Server 2008
Everyone should consider upgrading to Windows Server 2008. The newest generation in IP/TCP stacks can bring many benefits to enhance performance for the following functions: compound TCP, system recover, receiving window auto-tuning, and improving routing paths. One extremely informative resource available, “Enhanced Network Performance with Microsoft Windows Vista and Windows Server 2008” is a must have. Microsoft is constantly producing new data and results about their Windows SharePoint technology and products. Make sure you check in with Microsoft to obtain all the latest information on a regular basis.
The benefits of the 64-bit are abundant, although consider larger IP address space and larger chunks of data processing to make this effective. Actively consider sending garbage to 64-bit machines as many external factors can clog up IP address space with permanent memory portions; most systems automatically have a managed memory although you may still face situations where there is a delay in your web server response until the one thing or many things causing the delay can be moved to the memory.
In addition to this, consider monitoring loading performance, .NET CLR exceptions, and memory which will force you to consistently manage the collection activity of garbage files; these files can then be eaten up through scheduling a recycling function to run or programming garbage collection recycling when it has reached a certain point. The latter requires that you configure a random memory inception as well as requiring you to fully understand the requirements of your Web server; some of those requirements include hardware, loading of software, and residential services. Following this method is perfect as it will automatically maximize memory availability; at the same time this ensures that your servers for the Web continue to respond effectively and efficiently. This process also justifies any issues related to availability that may come into play. This may result in frequent recycling when designating or configuring an inception.
SharePoint and Wide Area Networks
When managing traffic that is generated by a remote office or satellite, consider accelerating WAN to assist in data replications. To accommodate large files being uploaded on a consistent basis by remote users using slower computer applications, adjust the settings on you IIS timeout program.
SharePoint Storage Design and Database Architecture
Other potential holdups that can affect performance are poor database architecture and the design of your store applications. Consider database distribution and, along with any hidden storage, provide as many linkages you can to data LUN’s. The database distribution is where database clustering is distributed between two or more situations.
Reduce the number of repeated visits you make to websites and take into consideration Kerberos authentication when available. If at all possible, avoid NTLM applications for authentication purposes.
Shout out to Steve and his history of SharePoint post through shirts