Throttling - Best Practices

12/3/2010

Check out the Part one of this series for indept analysis of Throttling in MOSS 2010.

 Best Practice for Throttling…

 A sharepoint list can support maximum of 50 million items with 50,000 individual rights. Now, that’s a gargantuan
number in itself. ..so here are some best practices for large lists/doc libraries… 

1.        Happy hours

You can always define at the Web Application level, the time frame where in queries returning large item counts need
to be run.  Normally the schedule of the tasks performing these queries should be mentioned here. It goes without
saying that the schedule time needs to be outside the load usage time. 

2.        Creating SharePoint indexed columns

Just like the Database columns, indexes can be created on the fields of a SharePoint list (MOSS 2010 only). It is
advisable to index the columns which are heavily used for search purposes.  This can be done by clicking Indexed
Columns link in List Setting Page.

Indexed columns in SharePoint MOSS 2010


Beware not to get carried away and create too many indexes.  As in SQL Server, the search is faster with indexes but there is a penalty of performance for update / insert operations. 

3. Organizing items into folders    

As much possible use folders to organize the content in your list. Folders not only provide grouping for the content but also creates an internal indexes.

4. Request Throttling

Request throttling is another key feature of MOSS 2010. If you enable Request throttling at central admin, SharePoint ( actually a SharePoint job running every  minutes ) will check the input parameters( CPU, Memory and Request in queue etc ) with the pre configured value to decide if the new http request can be served.  If not, then SharePoint will serve the existing requests without taking on a new one i.e SharePoint will enter into a throttled mode.  This way, rather than new users waiting indefinitely till the time out, they would get a nice error message requesting them to try the website after some time.  This feature is particularly useful in case you encounter considerable wait period for page rendering due to infrastructure issues.

Name

Email

WebSite

SharePoint Job throttling is the technique of regulating the performance of these tasks in any system. It can be used in situations where it is required to limit the amount of data that can be transferred in a unit of time.

StorageEdge provides comprehensive SharePoint job throttling features. When these jobs / tasks are run, various time slots can be configured to make sure that SharePoint application is not under continuous job processing stress.

This can be found in detail on www.alachisoft.com/blogs/storageedge/