Capacity Planning in SharePoint 2007

Capacity Planning Process of evaluating a technology … Deciding … Hardware … Variety of Ways Different Services

Hardware? Server Farm? SQL Server? Data Capacity? 64 bit? Users? Sites? Design Validation? Common Questions

Understanding of Platform and Features Configurations Options for Improvement Process for Requirements In This Session …

Components Planning Activities Planning

Business Requirements: – Software Boundaries – Throughput Targets – Data Capacity Testing and Tuning: – Hardware Components

Object Categories Software Scalability vs. Hardware Scalability RTM Test Results, Findings, and Recommendations from the Product Group Other Considerations Components Software Boundaries

Hierarchy

Software Boundaries Scalability SQL Server Stores Content Up and Out Millions of Documents Delegate Administration

Software Scalability Hardware Scalability Software Boundaries

Hardware Specifications: Computer RoleSpecifications Stand-alone 1 dual core Intel Xeon 2.0 GHz 64-bit processor, 2 GB RAM WFE 2 dual core Intel Xeon 2.8 GHz 64-bit processor, 4 GB RAM Database (SQL Server) 4 dual core Intel Xeon 2.8 GHz 64-bit processor, 32 GB RAM ClientsPentium III 1.2 GHz processor, 1 GB RAM Network: Gigabit Ethernet (one billion bits/sec) Farm Configurations Tested: DB’s1 WFE2 WFE3WFE4 WFE5 WFE6 WFE7 WFE8 WFE 1xxxxxxxx Product Group’s Test Environment

Software Boundaries Type of subsitePercent of total Team sites55% Document workspace20% Meeting workspace10% Blog10% Wiki5% Subsite Breakdown for Test

Software Boundaries

Guidelines ObjectRecommended MaxScopeObject Category Content DBs 100 per Web application Web applicationLogical architecture Site Collections50,000 per Content DBContent DBLogical architecture Web Sites 250,000 per Site Collection Site CollectionSite Object Documents 5 million per library (2000 per nested folder or view) LibrarySite Object Indexed Items 50 million per search index SSPSearch Object Web to DB Server Ratio 8FarmPhysical Object

Software Boundaries Throughput vs. Nr. of Web Servers (5:1) Other Recommendations – Carefully Plan – Minimize nr. Web apps and app pools – Limit nr. SSP – Plan for DB growth Software Boundaries

Estimates Usage Profile == User community behavior – Distribution of requests across content – Operation types and frequency Existing solution in place? Mine IIS Logs Leverage usage profiles provided in configurations Usage Profiles

Estimates Percentage of throughput Get home page15.00 Get cached document15.00 Get static document15.00 Get list page (HTML)10.00 Get list page (grid)10.00 Get list form errors5.00 Insert list item2.00 Edit list item2.00 Delete list item2.00 Insert document2.00 Synchronize with Outlook2.00 Delete document2.00 List URLs2.00 RSS (Really Simple Syndication)1.00 Start workflow0.75 Workflow task completion0.75 Add/remove user0.50 Sample Usage Profiles

Estimates Plan for Peak Concurrency!!!

Indexing Caching Enabled? Page Customizations Custom Web Parts Estimate Other Factors

Server Processing SQL Processing Client processing Javascript, CSS, AJAX, … Wire Transfer Bandwidth Estimate Latency

Custom Web Parts Round Trips Re-use client code … Design code for speed Profile you solutions Estimate Latency - Recommendations

Designed to Grow!!! – Server Resources: x32, x64, CPU, RAM, HDD – Server Farm Topology Restrictions Removed WFE, Query, Index, Excel Calc, Project, SQL Hardware How SharePoint Scales

Web Front-End Application Server Role Database Server Role Hardware Single Server Example

Hardware Multi-Server Example Web Servers App ServerSQL Server

Hardware Multi-Server Example (Scaling Out) Web Servers App Server SQL Server

WSS 3.0 and MOSS 2007 works on both 64-bit Recommended Larger # of Processors Enhanced Bus Architecture Next version will be 64-bit 64-bit HW Prioritization (SQL, Index, Excel, Search, WFE) Hardware 64-bit vs. 32-bit

Primary Metric: Document Storage Secondary Metric: Index Size Index Server: 30% - 50% of total size of all content indexed for a single server Query Server: 1 x index size Hardware Storage Considerations

Dedicated Server 64-bit HW and OS (High Recommendation) SQL Server 2005 SP2+ SQL Server I/O channels Scale Out and Up Hardware SQL Planning

Processor % Processor Time: _Total System: Processor Queue Length: (N/A) Memory: Available Mbytes: (N/A) Memory: Pages/sec: (N/A) Hardware Monitoring Physical Servers

SharePoint Capacity Planning Tool

Questions ? Twitter – Blog –

Thank You!!!