SharePoint and Office 365 Performance Best Practices
1 like682 views
This document provides best practices for optimizing performance in SharePoint and Office 365. It discusses techniques such as caching content in memory, distributing load across servers, optimizing database and search queries, and leveraging content delivery networks and bandwidth management when migrating to the cloud. The goal is to improve response times, reduce bandwidth usage, and ensure high availability.
SharePoint and Office 365 Performance Best Practices
- 1. SharePoint & Office 365 Performance Best Practices
- 2. @eshupps sharepointcowboywww.sharepointcowboy.com slideshare.net/eshupps linkedin.com/in/eshupps Eric Shupps Microsoft MVP
- 4. Build To Suit The Database Is King Cache In Make the Network Work For You Squeeze Those Bits Look Good But Perform Better
- 6. Database Users Search BI App Web Web Database Distrib Cache Distrib Cache Request Manager Request Manager Request Manager Office Web Apps Workflow Apps Azure O365
- 7. • Capacity • Load • Traffic Isolation • Web • Database • Service Applications • Search • Caching • Workflow • WAC • Indexing
- 8. Physical hardware resources Network connectivity Disk specifications File location Index maintenance High availability
- 9. Migration • Content archiving • Page cleanup • Data purging • Shrink files • Versions! Operations • Disk I/O • Index maintenance • Auto-growth • Quotas Disaster Recovery • Database size • Available bandwidth
- 10. • Provisioning overhead • Data isolation • Content storage • Query locks and throttling • Utilization • Recoverability • Resource Consumption • Availability System Services Site Collections Lists
- 11. CAN SHOULD
- 12. Page First request served from content database, output written to memory Subsequent requests for same resource read from memory Disk File-system objects cached by IIS Database objects not cached Object Commonly requested objects stored in memory Cross-site queries cached in memory
- 14. SharePoint aware rule based traffic shaping Throttling PrioritizationRouting Load Balancing
- 16. Machine Pool Routing Target Routing Target Execution Group Throttling Rules Health Weight Static Weight Health Weight Static Weight Routing Rule Routing Rule Routing Rule Routing Rule
- 17. Throttling Rules Rule 1 Rule 2 Rule 3 Execution Group 0 Rule 1 Rule 2 Rule 3 Execution Group 1 Rule 5 Rule 6 Rule 7 Execution Group 3 Rule 8 Rule 9 Rule 0 Machine Pool 1 Server 1 Server 2 Server 3 Machine Pool 2 Server 4 Server 5 Server 6
- 20. Page 1 Controls Chrome Content Page 2 Controls Chrome Content First Request Second Request Page 1 Controls Chrome Content Page 2 Controls Chrome Content Download Manager Download Manager First Request Second Request
- 21. Reduces ease of modification No versioning
- 23. 29 Requests / 570KB 21 Requests / 321KB
- 26. Migrations/Initial Data Transfer • Internal and External Bandwidth • ExpressRoute • Azure Storage Cloud • Content Delivery Network • Geographic Distribution (WAN link balancing) • Page contents
Editor's Notes
- #9: ERIC Physical hardware resources, network connectivity, disk size and speed, location of data files, configuration of shared storage—all aspects must be taken into consideration based on the size of the farm and the projected amount of data. SharePoint is both read and write intensive, so separating the I/O operations onto separate disks prevents excessive thrashing and cache hits Suggest - one set of disks for search databases, one for temporary databases, and still another for content databases Pre-size the databases up to the maximum recommended size (200GB) if space is available and set autogrowth to a fixed size (e.g. 10MB or 20MB). This will prevent SQL from expanding databases unnecessarily and insure that growth happens in a manageable fashion Defragment Database Indexes Indexes can become fragmented over time as new INSERT, DELETE and UPDATE operations are performed Plan for regular maintenance operations which include index defragmentation
- #11: ERIC