Expanding SharePoint Load Capacity

1. Expanding SharePoint Load Capacity Joel Oleson Microsoft

2. Who am I? SharePoint Guru BYU Grad Monkey Toy / EBay Collector Pogo Stick Jumping Extraordinaire Pseudo Surfer Wannabe Web Junky

3. Agenda Microsoft IT Best Practices & Lessons Learned Microsoft IT’s Solution Capacity Planning Scalability & Manageability Performance Tuning FY06 References Q&A

4. Agenda Microsoft IT Best Practices & Lessons Learned Microsoft IT’s Solution Capacity Planning Scalability & Manageability Performance Tuning FY06 References Q&A

5. Microsoft IT Environment

6. IT SharePoint StrategyUser to Enterprise Consistency

7. The Microsoft Site Hierarchy

8. Global SharePoint Deployment

9. Agenda Microsoft IT Best Practices & Lessons Learned Microsoft IT’s Solution Capacity Planning Scalability & Manageability Performance Tuning FY06 References Q&A

10. Capacity Planning Plan for 25-50GB Databases Limit Number & Size of Sites per Database Use 250 sites per database = 25GB @ 100MB Create a Profile (Microsoft Profile): Personal Site = 20MB Team Site = 60MB Design Defrag Schedule for Dbs Quarterly defrag Data Split into >100GB chunks for backup

11. System Sizing – Lessons Learned Small Farm Scenario (Small start here) Availability not a concern Cost restrictive 1-3,000 Users Medium Farm Benefits * (Med & Large start here) High Availability 99.9% Offloaded Indexing 1000-30,000 Users Large Farm Benefits Search Offloaded Indexing Offloaded Maximized for millions of documents 1000-30,000 Users Adding Front Ends 1 per additional 25,000 users

12. Americas Intranet Hardware

13. MSFT hardware - Itemized details

14. Agenda Microsoft IT Best Practices & Lessons Learned Microsoft IT’s Solution Capacity Planning Scalability & Manageability Performance Tuning FY06 References Q&A

15. SharePoint Growth and Scale

16. Usage Statistics on “Team”

17. Web CPU vs. Connections

18. Manageability with MOM 2005 MOM Packs Windows SharePoint Services SharePoint Portal Server 2003 SQL 2000 IIS 6 Microsoft Cluster Service Windows 2003 Server Web Site Monitoring Web Sites and Services MP

19. Agenda Microsoft IT Best Practices & Lessons Learned Capacity Planning Scalability & Manageability Performance Tuning FY06 References Q&A

20. Perf Counters to Know

21. Performance Tuning IIS Use few virtual servers Consolidate app pools for common apps, divide for poor performing Use web garden for max performance 3 W3WP work great one high usage virtual server on 4 GB box Limit WP Memory consumed to 500 or max 800MB Disable auto-rapid failure Use worker process logs & diagnostics

22. App Pool Worker Processes Properties

23. Performance Tuning Memory Web Front End Server Memory Use 4 GB RAM Add /3GB to boot.ini SQL Use 4 GB RAM Add /3GB to boot.ini Add –g512 to SQL Startup Parameters Use AWE and /PAE for 8GB Machines (High End) Limit databases < 300

24. Performance Tuning Backups OM Site Backups don’t scale and cause SQL blocking SharePoint Database Explorer for file restore (Reskit) Third party compressed database backup Use Private Network or Fiber attached tape Disk Pivoting -Utilize Passive Node SPSBackup for Index only

25. Performance Tuning Network Private network or Fiber attached tape to offload network Configure Front End & Backend NIC w/ separate routes Use Crossover or hub/switch for NLB & MSCS Clusters GigE gave us 3X performance

26. Performance Tuning Index Avoid Indexing twice Use Site Directory as Content Source Ease Scoping using Source Groups Use fewer Indexes Limit # of indexing threads Ad hoc content in larger index Important Content in smaller index 3 million documents indexed, 3 key indexes 12 total indexes3 million documents indexed, 3 key indexes 12 total indexes

27. Performance Tuning Misc. Kerberos vs. NTLM vs. Basic IIS Compression for Dynamic files Third Party – Offline, Replication, Acceleration SSL Offloading & IPSec WSS Hotfix (Post SP1) KB: 889385 (SharePoint Usage & Site Backup) IIS Hotfix: KB: 831464 (IIS Compression) SPS Search Hot fixes: http://support.microsoft.com/ph/2528 Single Threaded Ifilters

28. Agenda Microsoft IT Best Practices & Lessons Learned Capacity Planning Scalability & Manageability Performance Tuning FY06 References Q&A

29. IT FY06 Plans 64bit Windows 2003 SP1 & R2 SQL 2005 SharePoint SP2 A/A/P SQL Clusters –Scale out Optimize w/ third party solutions Integration with business developed ASP.NET Webpart solutions Search/Index Optimization and Ranking Like OWALike OWA

30. Agenda Microsoft IT Best Practices & Lessons Learned Capacity Planning Scalability & Manageability Performance Tuning FY06 References Q&A

31. References Microsoft IT Performance White Paper http://www.microsoft.com/downloads/details.aspx?familyid=8acf3b81-2db5-4079-b904-589d2d49bedd&displaylang=en Microsoft IT SharePoint Deployment WebCast http://msevents.microsoft.com/CUI/EventDetail.aspx?EventID=1032241971&Culture=en-US Microsoft IT Showcase WhitePapers on IW http://itweb/itshowcase/iw.htm SharePoint Resource Kit http://www.microsoft.com/technet/prodtechnol/sppt/reskit/default.mspx Business Benefits The key business benefits gained by Microsoft through the deployment of SharePoint Portal Server 2003 Shared Services included: Employees experienced improved productivity when they received a convenient and consistent intranet portal experience that made it easier for them to find and retrieve task-relevant knowledge and information. Systems administrators gained the ability to effectively and easily support a large world-wide intranet portal infrastructure consisting of a central intranet portal site and hundreds of business division, product group, regional and subsidiary portal sites deployed in three regional data centers Group and Division Portals Administrators of portal sites can take advantage of Shared Services that are common across a company. In general, use of services across an enterprise can reduce training costs and help desk calls. Furthermore, a Shared Services infrastructure avoids duplication of services for each portal. Network traffic created by a centralized indexing service is less than traffic created by numerous SharePoint Portal Server installations that independently crawl content. One example of the way in which Shared Services solve a business problem relates to the definition of search scopes for the collaboration platform. For example, if a group with content in one regional data center wants content and a portal hosted in that region, but also need it included in the search scope of a division portal hosted in a central data server, then they can associate it with a parent division portal and still include it in both the regional search and the divisional search for the organization. Enterprise Services The advantage of a deploying a common set of core portal services across Microsoft includes: Better decisions are made across the company when relevant information is easy for employees to find using enterprise search capabilities. Information workers are able to focus on business issues while Microsoft IT reduces costs for common portal services. Economies of scale are created for KNG and Microsoft IT because Shared Services enable them to implement shared best practices from a single central location and offer common high volume services across the global enterprise.Business Benefits The key business benefits gained by Microsoft through the deployment of SharePoint Portal Server 2003 Shared Services included: Employees experienced improved productivity when they received a convenient and consistent intranet portal experience that made it easier for them to find and retrieve task-relevant knowledge and information. Systems administrators gained the ability to effectively and easily support a large world-wide intranet portal infrastructure consisting of a central intranet portal site and hundreds of business division, product group, regional and subsidiary portal sites deployed in three regional data centers Group and Division Portals Administrators of portal sites can take advantage of Shared Services that are common across a company. In general, use of services across an enterprise can reduce training costs and help desk calls. Furthermore, a Shared Services infrastructure avoids duplication of services for each portal. Network traffic created by a centralized indexing service is less than traffic created by numerous SharePoint Portal Server installations that independently crawl content. One example of the way in which Shared Services solve a business problem relates to the definition of search scopes for the collaboration platform. For example, if a group with content in one regional data center wants content and a portal hosted in that region, but also need it included in the search scope of a division portal hosted in a central data server, then they can associate it with a parent division portal and still include it in both the regional search and the divisional search for the organization. Enterprise Services The advantage of a deploying a common set of core portal services across Microsoft includes: Better decisions are made across the company when relevant information is easy for employees to find using enterprise search capabilities. Information workers are able to focus on business issues while Microsoft IT reduces costs for common portal services. Economies of scale are created for KNG and Microsoft IT because Shared Services enable them to implement shared best practices from a single central location and offer common high volume services across the global enterprise.

32. IT Showcase:How Microsoft Does ITCustomer-ready resources from Microsoft IT IT Showcase on TechNethttp://www.microsoft.com/technet/itshowcase/ IT Showcase on Microsoft Serviceshttp://www.microsoft.com/itshowcase/

34. ADVISOR LIVE Web Update Page AdvisorEvents.com/cmt0506p.nsf/w/cmt0506ud This session WILL / WILL NOT have updates.

35. Thank you! Please remember to fill out your evaluation.