Rev Your Engines: SharePoint Performance Best Practices
•Download as PPTX, PDF•
1 like•187 views
This document discusses strategies for optimizing SharePoint performance, including: - Distributing the database and cache across multiple servers to improve scalability and availability. - Configuring request management to route requests based on rules to balance load and isolate traffic. - Caching frequently accessed content and data to improve response times. - Optimizing pages, components, and customizations to reduce page weight and client-side processing.
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Viewers also liked (15)
Similar to Rev Your Engines: SharePoint Performance Best Practices
Similar to Rev Your Engines: SharePoint Performance Best Practices (20)
More from SPC Adriatics
More from SPC Adriatics (20)
Recently uploaded
Recently uploaded (20)
Rev Your Engines: SharePoint Performance Best Practices
- 1. SharePoint Performance Optimization ERIC SHUPPS MVP
- 2. SPONSORS
- 3. About Me @eshupps sharepointcowboywww.sharepointcowboy.com slideshare.net/eshupps linkedin.com/in/eshupps Eric Shupps Office Server MVP
- 4. Agenda • Build to Suit • Make the Network Workf for You • The Database is King • Keep Traffic Moving • Cache In • Look Good but Perform Better
- 7. Internal Network • Capacity • Load • Traffic Isolation • Web • Database • Service Applications • Search • Caching • Workflow • WAC • Indexing
- 8. External Network Migrations/Initial Data Transfer • Internal and External Bandwidth • ExpressRoute • Azure Storage Cloud • Content Delivery Network • Geographic Distribution (WAN link balancing) • Page contents
- 9. Database Optimization 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. Database Distribution • Provisioning overhead • Data isolation • Content storage • Query locks and throttling • Utilization • Recoverability • Resource Consumption • Availability System Services Site Collections Lists
- 11. Database Fundamentals Physical hardware resources Network connectivity Disk specifications File location Index maintenance High availability
- 12. Request Management • SharePoint aware rule based traffic shaping • Throttling • Routing • Prioritization • Load Balancing
- 14. Request Management Components 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
- 15. Request Management Rules 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
- 16. Request Management Commands Enable Routing Get-SPWebApplication | Set-SPRequestManagementSettings –RoutingEnabled $true – ThrottlingEnabled $true Static Weighting Get-SPWebApplication | Get-SPRequestManagementSettings | Set-SPRequestManagementSettings –RoutingEnabled $true –ThrottlingEnabled $false –RoutingWeightScheme Static Health Weighting Get-SPWebApplication | Get-SPRequestManagementSettings | Set-SPRequestManagementSettings –RoutingEnabled $true –ThrottlingEnabled $false –RoutingWeightScheme Health
- 17. Request Management Commands Add Routing Target $web=Get-SPWebApplication -Identity http://portal.lonestar.com $rm=Get-SPRequestManagementSettings -Identity $web Add-SPRoutingMachineInfo – RequestManagementSettings $rm -Name SP2013A -Availability Available Create Routing Rule $w = Get-SPWebApplication -identity http://portal.lonestar.com$rmset = $w | Get- SPRequestManagementSettings$criteria = New-SPRequestManagementRuleCriteria -Property Url -Value ".*.xlsx" -MatchType Regex $mp = Add-SPRoutingMachinePool -RequestManagementSettings $rmset -Name DemoPool - MachineTargets ($rmset | Get-SPRoutingMachineInfo -Name SP2013A) $rmset | Add-SPRoutingRule -Name "Excel Rule" -Criteria $criteria -MachinePool $mp
- 18. Distributed Cache • Independent cache • No database persistence • Configurable memory allocation • Dedicated or collocated
- 19. Distributed Cache Dependencies Login Token Cache Access Cache Feeds (Activities,Likes, Mentions,Doc Actions) Search Query Web Part Last Modified Cache Security Trimming Cache OneNote Throttling App Token Cache View State Cache Default Cache
- 20. Distributed Cache Guidelines Deployment size Small farm Medium farm Large farm Total number of users < 10,000 < 100,000 < 500,000 Recommended cache size for the Distributed Cache service 1 GB (Default 10% RAM) 2.5 GB (Manual adjustment) 12 GB (Limit of16GB per server) Total memory allocation for the Distributed Cache service (double the recommended cache size above) 2 GB (Memory size must match in all servers) 5 GB 24 GB (32GB Max Limit) Recommended architectural configuration Dedicated server or co- located on a front-end server Dedicated server Dedicated server Minimum cache hosts per farm 1 1 1
- 21. Request Management Commands Provision $instanceName ="SPDistributedCacheService Name=AppFabricCachingService” $serviceInstance = Get-SPServiceInstance | ? {($_.service.tostring()) -eq $instanceName - and ($_.server.name) -eq $env:computername} $serviceInstance.Provision() Add Server Add-SPDistributedCacheServiceInstance Set Cache Size Update-SPDistributedCacheSize -CacheSizeInMB 1200
- 22. User Interface • Client-side rendering • Optimized markup • Minimal download • Image renditions • Device Channels • Content by search
- 23. Customizations Page Components • Markup • Navigation • Images • Scripts • Code • Web and App Parts Branding • Styles • Resources • Master Pages • JavaScript Injection
- 25. Minimal Download 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
- 26. Page Rendering
- 27. Page Weight 29 Requests / 570KB 21 Requests / 321KB
- 29. thank you questions? live ratings BLOG URLTWITTER HANDLE spca.biz/HHVA
Editor's Notes
- ERIC
- 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