Dealing with Performance in SharePoint Server - SPSVancouver
•Download as PPTX, PDF•
0 likes•204 views
SharePoint is slow. Pages take ages to load. The throbber spins forever. "Working on it..." becomes the SharePoint motto. How can you tell if your SharePoint farm is under-performing? Why is it slow? What can you do to improve SharePoint's performance? In this talk we'll look at tools available to SharePoint and IT administrators to help them assess the performance of their SharePoint farm to come up with a plan for improvement.
Recommended
More Related Content
What's hot
What's hot (20)
Similar to Dealing with Performance in SharePoint Server - SPSVancouver
Similar to Dealing with Performance in SharePoint Server - SPSVancouver (20)
Recently uploaded
Recently uploaded (20)
Dealing with Performance in SharePoint Server - SPSVancouver
- 1. SharePoint Saturday Vancouver Dealing with Dealing with slow performance in SharePoint Server http://bonzai-intranet.com/
- 2. Jason Warren • Bonzai Intranet for SharePoint • Microsoft Office Servers and Services MVP (SharePoint MVP) Infrastructure Architect @jaspnwarren jason@dynamicowl.com Jasonwarren.ca
- 3. Today’s Agenda Monitoring Performance Troubleshooting Performance Q&A SPS Vancouver 2017: Dealing with SharePoint Performance http://bonzai-intranet.com/
- 4. Intended Audience SPS Vancouver 2017: Dealing with SharePoint Performance http://bonzai-intranet.com/ • Anyone who is asked “Why is SharePoint slow?” • SharePoint Administrators • Server Administrators • Developers
- 5. Why Monitor Performance? SPS Vancouver 2017: Dealing with SharePoint Performance http://bonzai-intranet.com/ • Confirm hardware and applications are performing as expected • Identify performance issues before they cause problems • Look at performance in a measurable and quantified way • Instead of “slow” its “this slow”
- 6. SharePoint Monitoring SPS Vancouver 2017: Dealing with SharePoint Performance http://bonzai-intranet.com/ • Microsoft’s Performance Monitoring Recommendations • Optimize performance for SharePoint Server 2013 • https://technet.microsoft.com/en-ca/library/jj721440.aspx • Primary source for data: Windows performance counters • Tools available in Windows + 3rd party
- 8. Performance Monitoring SPS Vancouver 2017: Dealing with SharePoint Performance http://bonzai-intranet.com/ • Out of the box tools aren’t great for representing and understanding the data • Performance Analysis of Logs (PAL) • https://pal.codeplex.com • Historical performance can be used as a baseline
- 9. Performance Baselines SPS Vancouver 2017: Dealing with SharePoint Performance http://bonzai-intranet.com/ • Why have a baseline?
- 10. Monitoring Recap SPS Vancouver 2017: Dealing with SharePoint Performance http://bonzai-intranet.com/ • Be proactive: use (a) performance monitor • Look at your performance data with your PAL • Keep a performance baseline • Do these things so you can ask the business for hardware before you can’t live without it
- 11. Troubleshooting Performance SPS Vancouver 2017: Dealing with SharePoint Performance http://bonzai-intranet.com/
- 13. Troubleshooting Recap SPS Vancouver 2017: Dealing with SharePoint Performance http://bonzai-intranet.com/ • Browser tools/fiddler to determine SharePoint/external issue • SPRequestGuid Correlation Id Merge-SPLogFile • ULS Logs and Execution Time for behind-the-scenes slowness • Automate activity for intermittent issues
- 16. Monitoring Tools SPS Vancouver 2017: Dealing with SharePoint Performance http://bonzai-intranet.com/ • Monitoring and maintaining SharePoint Server • technet.microsoft.com/en-us/library/ff758658.aspx • Performance Monitor (PERFMON.EXE – included in Windows) • Performance Analysis of Logs (PAL) • pal.codeplex.com/ • Merge-SPLogFile • technet.microsoft.com/en-us/library/ff607721.aspx • ULS Viewer • www.microsoft.com/en-ca/download/details.aspx?id=44020
- 17. Troubleshooting Tools SPS Vancouver 2017: Dealing with SharePoint Performance http://bonzai-intranet.com/ • Browser Developer Tools (Chrome, FireFox, IE) • Fiddler • www.telerik.com/fiddler • Merge-SPLogFile • technet.microsoft.com/en-us/library/ff607721.aspx • ULS Viewer • www.microsoft.com/en-ca/download/details.aspx?id=44020
- 18. bonzai-intranet.com @bonzaiintranet sales@bonzai-intranet.com +1 (844)-547-2662 675 W.Hastings, Vancouver B.C. V6B 1N2 Thank You!
Editor's Notes
- Today’s talk is for anyone who has to explain to SharePoint users why SharePoint is slow. You may be responsible for a SharePoint farm, or the underlying infrastructure SharePoint runs on, or maybe you develop SharePoint solutions and users think the slowness is because of your buggy code.
- You're providing SharePoint as a service to your users and they use SharePoint to store and access information and applications. They expect SharePoint will let them access their information in a reasonable amount of time and without errors. Monitoring performance ensures the farm is meeting the user's expectations. It gives you insight into bottlenecks and insufficient or failing hardware that gives you the data you need to go to the business to acquire new or better hardware. You can quantify performance so instead of saying “SharePoint is slow” you can say “On average it takes 20 seconds for pages to load in SharePoint because we have an insufficient number of processors to handle the requests which is unacceptable.”
- Microsoft has recommendations for how to monitor SharePoint performance. These recommendations are in a guide published on TechNet, the latest available version is for SharePoint 2013. If you have SharePoint 2016 this guide still applies. The guide recommends using Windows performance counters with the Performance Monitor tool that comes in every version of Windows. Performance counters provide metrics for the hardware and software subsystems in a Windows machine. Things like processor use, disk queues, bytes read, memory used, etc. When you install Microsoft software additional counters specific to the application are installed. As well as perfmon, there are third party products that provide a more robust monitoring experience (notifications, real-time graphs, enterprise-wide views) but still rely on performance counters for their data.
- Out of the box PERFMON is great at collecting data, but not so great for analyzing or understanding it. I recommend using PAL or if you have another product that performs similar analysis. And because you have an HTML file with pictures, you have data that you can use as a baseline to compare with for future performance problems.
- Why have a baseline? With a baseline, you have a historical record that shows you how your farm was performing. You don’t need to guess or try to remember. And when you have a historical record, you can compare performance in the past, to performance now. If a user comes to you and says “SharePoint is slow” and you compare the performance to what it was a couple months ago and you see a difference, there’s likely something to that user’s complaint. If you don’t have anything to compare to, you can’t objectively say “yes, it was performing well before, but now it is not.” With a tool like PAL you hang onto the reports after you generate them and compare them when you need to.
- So to recap, You want to be proactive with monitoring performance. If there’s a performance issue, you can’t peer back in time to see how your farm performed if you didn’t track and record it. BY setting up a data collection log now, you’re giving yourself another troubleshooting resource later. Use a tool like PAL to quickly analyze the data and provide reports you can show to the business. Keep those reports, so you have a baseline you can use to compare with current performance.