Upload
kathleen-burns
View
218
Download
1
Tags:
Embed Size (px)
Citation preview
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
ComponentsSoftware Boundaries
Software Boundaries
Farm
Servers
Web Applications
Databases
Site Collections
Sites
Lists
Items
Hierarchy
Software BoundariesScalability• SQL Server Stores Content• Up and Out• Millions of Documents• Delegate Administration
• Software Scalability• Hardware Scalability
Software Boundaries
Software Boundaries
Hardware Specifications:Computer Role SpecificationsStand-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
Clients Pentium III 1.2 GHz processor, 1 GB RAMNetwork: Gigabit Ethernet (one billion bits/sec)Farm Configurations Tested:
DB’s 1 WFE 2 WFE 3WFE 4 WFE 5 WFE 6 WFE 7 WFE 8 WFE
1 x x x x x x x x
Product Group’s Test Environment
Software Boundaries
Type of subsite Percent of total
Team sites 55%
Document workspace 20%
Meeting workspace 10%
Blog 10%
Wiki 5%
Subsite Breakdown for Test
Software Boundaries
Software Boundaries
Software Boundaries
Software Boundaries
Software BoundariesGuidelines
Object Recommended Max Scope Object CategoryContent DBs 100 per Web application Web application Logical architecture
Site Collections 50,000 per Content DB Content DB Logical architectureWeb Sites 250,000 per Site
CollectionSite Collection Site Object
Documents 5 million per library (2000 per nested folder or view)
Library Site Object
Indexed Items 50 million per search index
SSP Search Object
Web to DB Server Ratio
8 Farm Physical 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 page 15.00
Get cached document 15.00
Get static document 15.00
Get list page (HTML) 10.00
Get list page (grid) 10.00
Get list form 7.00
404 errors 5.00
Insert list item 2.00
Edit list item 2.00
Delete list item 2.00
Insert document 2.00
Synchronize with Outlook 2.00
Delete document 2.00
List URLs 2.00
RSS (Really Simple Syndication) 1.00
Start workflow 0.75
Workflow task completion 0.75
Add/remove user 0.50
Sample Usage Profiles
EstimatesPlan for Peak Concurrency!!!
• Indexing• Caching Enabled?• Page Customizations• Custom Web Parts
EstimateOther Factors
• Server Processing• SQL Processing• Client processing• Javascript, CSS, AJAX, …• Wire Transfer• Bandwidth
EstimateLatency
• Custom Web Parts• Round Trips• Re-use client code …• Design code for speed• Profile you solutions
EstimateLatency - Recommendations
• Designed to Grow!!!– Server Resources: x32, x64, CPU, RAM, HDD– Server Farm• Topology Restrictions Removed• WFE, Query, Index, Excel Calc, Project, SQL
HardwareHow SharePoint Scales
• Web Front-End• Application Server Role• Database Server Role
HardwareSingle Server Example
HardwareMulti-Server Example
Web Servers App Server SQL Server
HardwareMulti-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)
Hardware64-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
HardwareStorage Considerations
• Dedicated Server• 64-bit HW and OS (High Recommendation)• SQL Server 2005 SP2+• SQL Server I/O channels• Scale Out and Up
HardwareSQL Planning
• Processor % Processor Time: _Total• System: Processor Queue Length: (N/A)• Memory: Available Mbytes: (N/A)• Memory: Pages/sec: (N/A)
HardwareMonitoring Physical Servers
SharePoint Capacity Planning Tool
Questions ?
• Twitter - @noidentity29• Email – [email protected]• Blog – www.shannonbray.com
Thank You!!!