SharePoint performance is down, factors to be considered
Check out Best Alternative to InfoPath -> Try Now
Friends, it would be of a great deal and help if we had an overall description of ‘what has occurred’ during determining the factors of down SharePoint performance.
Below I am listing some of the key points which had clicked to my mind.
Troubleshooting SharePoint Performance Issues
- Is the issue present on all content databases and sites in a web application?
- If one site is having issues check the URL for the content database the site resides. – This can help determine if the issue is site-specific or larger. Is the issue present on all content databases and sites in a web application?
- If the content database URL has issues then check other Content databases in the same web application.
- If the web application is having issues validate other web applications in the same method.
- Compare web applications from each SQL Server, this can help determine if there is a SQL issue.
- Is the issue present on all WFE’s?
- Test from the WFE’s and from a desktop – This can help locate any issues with Network or Load Balancer
- Check WFE events, ULS, IIS, performance monitor
- Do WFE’s have high CPU?
- Is High CPU on one process/web application
- Capture all processes organized by CPU utilization
- Determine what web application is related to the processing as necessary
- IS SQL performing well?
- Have the correct Teams such as SA and DBA to validate Wintel Server or SQL for any issues.
- Involvement of all internal teams should be required and record everything for easily sharing and record.
- When involving Microsoft share all event logs, IIS logs, ULS logs, and performance monitor logs captured with them.
SharePoint 2010/2013 performance issue reasons (Server Side Object Model Code)
Now, we will discuss some reasons why performance issue causes in SharePoint 2010/2013. Basically when we are using SharePoint server object model code.
We should be very careful while writing SharePoint Object Model code. SPDisposeCheck is a tool which tells us about whether all the objects are disposed properly or not.
Here is some reason that might cause performance issues in SharePoint 2013/2016.
- If you do not dispose properly of SPSite and SPWeb objects, then it will cause performance issue of your site.
- Suppose you have a larger list, then you should execute a query on the list rather than iterating through large items.
- If you are avoiding SPSiteDataQuery, instead of for each loop to aggregate SharePoint data.
- Using recursive method calls to iterate through information in every site within a site collection.
- If you fail to close external connections after use, then it might cause a performance issue of your SharePoint site.
- While connecting to external systems and fails to trap timeouts.
- If you are using session state then you should be very careful because overuse or improper use of session state will cause a huge performance issue.
- Not using caching like blob caching, Profile caching, Output Caching, Object Caching, etc.
A SharePoint performance troubleshooting guide from Idera would also help you to determine the factors to be considered during troubleshooting down SharePoint performance.
SharePoint Online FREE Training
JOIN a FREE SharePoint Video Course (3 Part Video Series)