Fine Tuning Your Microsoft SharePoint Server 2010 Environment

1. Required Slide SESSION CODE: OSP310 Fine Tuning Your Microsoft SharePoint Server 2010 Environment Shannon Bray Technical Architect Planet Technologies Mike Watson Principal Consultant SeriousLabz

2. IntroductionsShannon Bray • SharePoint 2010 MCM Candidate: Oct. Rotation • MCT, MCITP, MCPD (e), MCSD, MCDBA, … • President of COSPUG • Technical Architect for Planet Technologies • Proud member of the WHO DAT Nation!!!

3. IntroductionsMike Watson • Owner & Principal Consultant SeriousLabz • Specialties • Performance/Health analysis & mitigation • High Availability & Disaster Recovery • Design, deployment, and monitoring • Formerly • Product Manager for Quest Software • Microsoft • SharePoint Customer Advisory Team vTeam • Center of Excellence • BPOS-D & BPOS-S • Microsoft IT (Internal SharePoint) 10 Years in SharePoint as handsome as ever!

4. SharePoint 2010 is Cool! Most awesome SharePoint yet! Broader functionality Cross browser support, BCS, compliance Deep feature improvements Fast Search Entirely new capabilities Office Web Apps Easier to deploy & manage Service apps, PowerShell, monitoring, reporting Easier to build & extend Visual Studio 2010 templates, SP Designer, No code solutions

5. Coolness Comes at a Cost • More complexity • Steeper learning curve • More concurrency • More tweak points

6. What You Will Learn • SharePoint 2010 ramifications on Hardware/Software • How to optimize the frontend • How to optimize the backend

7. What’s New in SharePoint 2010 Deployment Considerations on Capacity and Performance

8. Frontend Optimizations How to optimize web and application servers for better capacity and performance

9. CapacityDefinition “Actual or potential ability to perform, yield, or withstand”

10. CapacityQuestions • How much hardware do we need? • Do we need SQL Server? • How much data can we store? • How many users can our environment support? • How should we set up our Service Applications? • How do we validate our design?

11. CapacityComponents • End-User Latency • Throughput • Data Sets and Storage

12. LatencyDefinition “The measure of time delay experience in a system”

13. LatencyTools • IE8 JS Profiler – Hit [F12] in IE8 • VRTA (Virtual Round Trip Analyzer) • Visual Studio Team System 2010 • Fiddler 2

14. Latency Tools Shannon BrayTechnical ArchitectPlanet Technologies DEMO

15. ThroughputDefinition “The quantity of amount of raw material processed within a given time”

16. ThroughputTools • Logging Database • Developer Dashboard • Large List Throttling • Throttling Excessive Client Load

17. Throughput Tools Shannon BrayTechnical ArchitectPlanet Technologies DEMO

18. Capacity Issues • Server Processing  Latency, Throughput, Storage • Wire Transfers  Latency, Throughput • Bandwidth, Size of Downloads  Latency, Throughput • Network Security  Latency • Network Configurations  Latency • Software Boundaries  Latency, Throughput • Security Trimming  Latency • Code: Round Trips, AJAX, JavaScript, CSS, etc.  Latency, Throughput

19. Tweaking the System • Validating Requirements • Network Security • Network Configurations • Boundaries • Custom Software • Caching

20. Tweaking the SystemValidating Requirements

21. Tweaking the SystemNetwork Security • Anonymous • Kerberos • NTLM • Basic • Forms

22. Tweaking the SystemNetwork Configurations • Network Interface Card (NIC) • NIC Settings • Inbound / Outbound • Switches • Routers • Domain Controllers

23. Tweaking the SystemBoundaries • Software Scalability • Hardware Scalability

24. Tweaking the SystemBoundaries Limits • Improved • 100 Million Items per Search Index (1 Billion with FAST) • Tens of Millions of Documents / Items in a single list • View/Query 5000 items at a time • Remains • 150,000 Site Collections per WebApp • 50,000 Site Collections per Content DB • 100 GB Content DB (W/R)

25. Tweaking the SystemBoundaries Limits • Service Applications • Application Pools • Zones • Content Databases • Site Collections • Sites • Host-Name Site Collections

26. Tweaking the SystemPhysical Limits • Processor • Processor Queue Length • Memory: Available in Mbytes • Memory: Page / Sec

27. Tweaking the SystemCustom Code • Custom Web Parts • SQL Server round trips • SQL Server CPU utilization • Page download size • Client-side code efficiency • AJAX callbacks

28. Tweaking the SystemCaching • BLOB Cache • Output Cache • Object Cache

29. Tweaking the SystemHTTP Request

30. Caching Shannon BrayTechnical ArchitectPlanet Technologies DEMO

31. Backend Optimizations How to optimize SQL server and storage for better capacity, health, and performance

32. “In Soviet Russia we have saying… meet the new boss. Same as the old.”

33. It’s JUST SQL! • 2010 Supports: • SQL Server 2005 SP3 X64 or • SQL Server 2008 SP1 X64 CU2 • For SQL in general: • The more processors the better (4 – 8 or more cores) • The more memory the better (16GB – 129GB) • The more disks the better (> 2000 IOPS) • Read SQL Requirements: http://technet.microsoft.com/en-us/library/cc298801.aspx

34. BLOB Storage Mike WatsonPrincipal Consultant SeriousLabz DEMO

35. SQL FileStream Performance

36. It’s all about the provider • The provider is the key to your happiness and potential • As usual, in the box or “free” is not best • Limitations of SQL Filestream provider • Can’t mirror • Can’t specify multiple blob locations per DB • MUST use local NTFS storage • NO business logic

37. Optimization Strategy

38. Cheap Fast Good Pick 2!

39. Identify the Workload

40. Workload Characteristics • READ Centric • Less disk intensive – Optimize for data reads • Focus on minimization through caching on the frontend • WRITE Centric • More disk centric – Optimize for logging • Scale across disks

41. Pregrow and Never Autogrow

42. #x Allocate as many disks as needed to SQL Temp Logs Search Data

43. Think Disk IO! Not Disk Capacity!

44. Calculating Disk IOAn Example

45. Best PracticesSQL Disk IO • Allocate separate and dedicated disks with the following specifications: • * Raid 1 or variants (0+1, 1+0) • ** Depends on type and amount of content being indexed • *** 2000 IOPS minimum. Plan on 1500 IOPS per simultaneous crawl. (e.g. 3 crawls = 4500 IOPS) • **** Use Raid 5 when redundancy needs are met with replication

46. Use RAID 10

47. <Contacts> <MikeWatson> <email> mike.watson@seriouslabz.com /> <twitter>www.twitter.com/mikewat /> <blog>www.sharepointmadscientist.com /> <web>www.seriouslabz.com /> </MikeWatson> <ShannonBray> <email> sbray@go-planet.com /> <twitter> www.twitter.com/noidentity29 /> <blog> www.shannonbray.com /> <web> www.go-planet.com /> </ShannonBray> </Contacts>

48. Play the Microsoft Office & SharePoint Track Tag Contest Download the Microsoft Tag Reader Open the internet browser on your mobile phone and visit http://gettag.mobi Grand Prize (1) Xbox 360 Prize Package and Microsoft® Office 2010 Daily Prizes 40 copies of Microsoft® Office 2010 Come to the Expo Hall – Yellow Section OSP Info Desk for Official Rules & Collect Additional Tags from all OSP Track Sessions, Speakers and Expo Hall!

49. Q & A Questions?

50. Required Slide Resources Learning • Sessions On-Demand & Community • Microsoft Certification & Training Resources www.microsoft.com/teched www.microsoft.com/learning • Resources for IT Professionals • Resources for Developers • http://microsoft.com/technet • http://microsoft.com/msdn