Performance Testing and Optimizing SharePoint Websites #spc11 @kieferconsult

Brian Rodriguez and Ryan Sockalosky
Microsoft Presentation

• Plan for all consumers
• Browsers
• Office apps
• Search and Services
• 3 hardest server calls
• SQL
• Authentication
• Blob
• Agents
• Use a 75/25% Read/Write ratio
• CPU around 50%
• Data-driven test within Visual Studio team test
• Use a web test project
• Data: Add users, sample docs, search terms, and configuration elements
• Watch for timer jobs
• Verify load balancing
• sample rate: 5 sec for an hour, 15 seconds for 4 hours, 60 seconds for a 24 hour+
• Use Performance Monitor
• Run load test and make 1 change at a time while monitoring performance
• Optimize
• Blob cache
• Blob cache fill ration should be < 90%
• web.config configuration per WFE
• SQL
• Disk I/O wait time
• asp.net wait time
• latency
• CPU
• SQL IOPS
• Fix with TempDBs storage device upgrades
• See slide deck for other optimization techniques
• Output Cache
• Don't output cache search results
• Configure at: Site Collection, Site, or Page Layout
• Object Cache
• Memory
• Use for cross list queries

If you don't know how much it's going to cost, it'll cost a lot.
If you aren't testing it, your measurements are wrong. If you aren't measuring, you can't make it faster.