SharePoint Performance Improvement with custom applications

Notes:

1.1       Web References
http://msdn.microsoft.com/en-us/library/aa292118(v=vs.71).aspx
http://blog.mastykarz.nl/pageasynctask-improve-performance-website/\
http://srinutamada1.wordpress.com/2012/06/15/sharepoint-2010-performance-improvement-steps/
http://weblogs.asp.net/scottgu/archive/2006/04/11/442448.aspx
It is always recommended that you publish website in Release Mode

The following documented resources from the Internet are applicable to, or have been used to compile and validate the content of, this document:

·          SharePoint 2010 Developer Best Practices Resource Center.

·         SharePoint Developer Center: http://msdn.microsoft.com/en-us/sharepoint/default

·         Best Practices with SharePoint Foundation: http://msdn.microsoft.com/en-us/library/ee556427(office.14).aspx 

·         http://www.sharepointdevwiki.com/

SharePoint Performance improvement:

1. Impersonation can significantly affect performance and scaling. It is generally more expensive to impersonate a client on a call than to make the call directly. 

2. http://social.msdn.microsoft.com/Forums/sharepoint/en-US/610bdb2b-387b-4e68-b487-547f9cb5651c/improving-performance-on-sharepoint-webparts

3. Using PageAsyncTask to improve the performance of your website

     

5.    SharePoint 2010 Performance – Improvement Steps

a.    Use XSLT instead of grids.

b.    Disable view state if you are not performing any use actions.

c.    Don’t throw exceptions; re throw exceptions are much costlier in terms of memory consumption and execution.

d.    Minimize exception handling blocks, use exception block where ever you are not able to handle or pretend exceptions.

e.     

6.    Don’t run production ASP.NET Applications with debug=”true” enabled

a.    If you publish using Debug mode, your generated files have debugging enabled and that will impact the performance.

b.