SharePoint Capacity Planning Balancing Organiza,onal Requirements with Performance and Cost

Transcription

1

2 SharePoint Capacity Planning Balancing Organiza,onal Requirements with Performance and Cost Kirk Devore / J.D. Wade SharePoint Consultants Horizons Consul;ng

3 Agenda Expecta;ons Defining SharePoint Capacity and Performance Anatomy of SharePoint Performance Considera;ons Focus from the bohom up SQL Focus WFE Focus APP Servers Virtualiza;on of SharePoint Servers General SharePoint Performance Considera;ons Q&A

4 Expecta;ons Balancing Organiza,onal Requirements with Performance and Cost 200 Level Session Not deeply technical / Not beginner level Technical info balanced with business considera;ons Discuss the considera;ons and introduce best prac;ces Won t hurt my feelings if you change sessions at this point

5 Define SharePoint Capacity and Performance What does SharePoint performance mean in your enterprise? May sound funny, but it is a ques;on that needs to be asked. What are you using SharePoint for? Unlike Exchange where every enterprise uses it the same way. No single deployment architecture across companies. Diversity of content stored in SharePoint. Other Considera;ons that ;e in Business Processes that spike usage only once a month, quarter, etc.. What are your disaster recovery SLAs? o May invalidate other SharePoint design limits Almost Always: Throughput is key BoHom Line: Requests Per Second & Response Time

6 Op;miza;on What things come to mind when I say: I want to op,mize my SharePoint environment? All of these are possible at the same ;me if.. you have unlimited resources. When you don t have unlimited resources: Op#mize = Compromise

7 Anatomy of SharePoint Performance Considera;ons SharePoint IIS.NET Framework WWF (workflows) SQL DISK SUBSYSTEM OPERATING SYSTEM NETWORK AUTHENTICATION ANTI- VIRUS

8 SQL Considera;ons Disk I/O Speed is primary Almost everything else is secondary to this. TempDB Considera;ons Has the broadest impact on SharePoint performance of all DBs SharePoint uses the TempDB frequently By default it is created on C: of the SQL server Should be on a dedicated RAID 10 drive array o Fast Reads & Writes o Most # of disks required & most cost per GB Should configure SQL for mul;ple physical files Create # of tempdb data files equal to # of cores/cpu. Configure tempdb data file size based on this equa;on: [MAX DB SIZE (KB)] X [.25] / [# CORES] = DATA FILE SIZE (KB)

9 SQL Considera;ons Pre- Size DBs and Logs Auto growth has an impact on performance o Default: 2Mb file and grows 1MB as needed. Size DB for 1 years growth Incremental Growth o Grow by % o Grow by Fixed MBs Keep content DBs under 100GB in size DB Locking issues increase as size grows Can have many site collec;ons in a single content DB o Move site collec;ons to new DB if needed A Site Collec;on is confided to a single content DB What if I have a single site collec;on > 100GB?

10 SQL Considera;ons Very Large Content Databases > 100GB of content Use mul;ple data SQL files for Large content databases Recommenda;ons for best performance: o Distribute the files across separate disks. o The number of data files should be less than or equal to the number of core CPUs. [MAX DB SIZE] / [# CORES] = DATA FILE SIZE Full Details hhp://technet.microsop.com/en- us/library/cc aspx

11 SQL Considera;ons Priority: Allocate Fastest Drives to: 1. Tempdb database 2. Database transac;on log files 3. Search database (if applicable) 4. Content Database data files If mainly sta;c content, then move #2 to the bohom.

12 SQL Considera;ons SQL Version Impact on Performance SQL 2000 (SP3) o Supported but consider this a legacy plauorm SQL 2005 o Performance Gains SQL 2008 o Backup Compression o Capacity Gains Farm size SQL 2000 avg RPS SQL 2005 avg RPS Change Small % Medium % Large % Extra- large %

13 Anatomy of SharePoint Performance Considera;ons SharePoint IIS.NET Framework WWF (workflows) SQL DISK SUBSYSTEM OPERATING SYSTEM NETWORK AUTHENTICATION ANTI- VIRUS

14 WFE Considera;ons WFE is the server in the farm the user hits directly Front door to rest of farm Basic Transac;on: o Get Request from user o Pass request on to SQL Server o Get results from SQL Server o Apply Security Trimming o Render pages before returning to user What are key capacity and performance considera;ons?

15 WFE Considera;ons Standard Capacity\Performance Considera;ons CPU U;liza;on NIC U;liza;on Memory U;liza;on Easy to add addi;onal WFEs to farm Fail over considera;ons usually call for mul;ple WFE s first Sopware NLB vs. Hardware NLB o Visit F5 Booth Virtual vs. Physical Considera;ons Best place to start with virtualiza;on in a farm

16 WFE Considera;ons Query Service running on WFE considera;ons Can see search query performance improvement if Query service also running on WFE. Remember Op;mize = Compromise IIS App Pool Recycling Standard Prac;ce of IIS o Set to recycle each night Impact on SharePoint users First User Impact o Warm- up scripts to minimize impact Idle Time Outs on App Pools o Central Admin App Pool Time out aper 10 mins o Content App Pool - Do not let it ;me out. IIS Compression Feature Can be important if users across WAN Helps if network bandwidth is your bohle neck Drives up CPU u;liza;on both server and client o Hardware based solu;ons exist that don t drive up CPU u;liza;on

17 Anatomy of SharePoint Performance Considera;ons SharePoint IIS.NET Framework WWF (workflows) SQL DISK SUBSYSTEM OPERATING SYSTEM NETWORK AUTHENTICATION ANTI- VIRUS

18 APP Server Considera;ons Shared Roles on Applica;on Servers Need to evaluate how each of the applica;on roles are used in your enterprise before deciding what roles can share a server. o Search Services Index Role & Query Role o Excel Calcula;on Services (enterprise) o Infopath Forms Services (enterprise) o Business Data Catalog (enterprise) Search Performance Considera;ons Could be it s own session Processor and I/O Intensive on Index Server during crawl Index server Build Index Files & Copy to Query Servers Query Server Read Index Files Excel Services Memory and Processor Intensive InfoPath Forms Services Processor Intensive

19 General SharePoint Considera;ons Sopware Boundaries that impact performance Sopware boundaries in SharePoint could consume an en;re presenta;on by themselves.. Not enforced by plauorm like size quota Some Key Boundaries 2000 items in a single rendered view Index the field that the view is sorted on In doc library, folders give beher performance than indexed views

20 General SharePoint Considera;ons Other items that can impact performance Web Parts that are hidden on a page, instead of being removed o Hidden web parts take just as much ;me to load Custom Code o If you see memory leak issues on servers, look here first. Customized Sites Templates (Unghosted) o Pull from SQL rather than local 12 hive on WFE WAN Considera;ons Performance can be large issue if most of your users are across WAN links. 3 rd Party Solu;ons can yield big gains in throughput. Not SP Specific, but some enhanced for SP o F5, Certeon, Citrix, Cisco

21 General 32 Bit vs 64 Bit Info 64bit has become default recommenda;on for new designs because of many performance advantages. Addressable Memory Bus Architecture Parallel Processing improvements Don t mix 32 & 64 Bit servers within a ;er All WFEs, All Applica;on Servers, All SQL Next version of SharePoint very likely 64 Bit only Priority of roles for moving to 64- bit systems: 1. SQL Server servers 2. Indexing servers 3. Excel Services servers 4. Query servers 5. WFE servers

22 SharePoint Virtualiza;on Important in cost containment considera;ons What is supported by Microsop for SharePoint? MS Technologies = YES o Virtual Sever 2005 & Hyper- V 3 rd Party = YES. If.. o If 3 rd Party cer;fied by Microsop's SVVP program. o VMWare ESX is supported Caveats MS Support may require you to reproduce the issue without the 3 rd party technology. Snapshot not supported in mul; server farms. o Both MS and 3 rd party technologies

23 SharePoint Virtualiza;on Virtualiza;on of SharePoint Roles Order of considera;on 1. WFE Roles 2. Query Server 3. Index Server 4. Excel Calc \ InfoPath Forms Services 5. SQL Server 1. Supported, but not recommended. Don t introduce a single point of failure o Example: All WFE servers on a single host o Can mix Physical and Virtual instances of a role

24 Addi;onal SharePoint Considera;ons Key Resource from Microsop Plan for performance and capacity (Office SharePoint Server) hhp://technet.microsop.com/en- us/library/cc aspx o Links to 18 addi;onal white papers and case studies. UK SharePoint Team hhp://blogs.msdn.com/uksharepoint/ o Recently published work on virtualiza;on

25 Ques;ons

26