• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Share point 2010 performance and capacity planning best practices
 

Share point 2010 performance and capacity planning best practices

on

  • 3,378 views

 

Statistics

Views

Total Views
3,378
Views on SlideShare
3,378
Embed Views
0

Actions

Likes
1
Downloads
46
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Share point 2010 performance and capacity planning best practices Share point 2010 performance and capacity planning best practices Presentation Transcript

    • SharePoint 2010Performance and Capacity Planning Best Practices Eric Shupps SharePoint Server MVP
    • About Me• SharePoint Server MVP• President, BinaryWave• Microsoft Patterns & Practices (spg.codeplex.com)• CKS:DEV (cksdev.codeplex.com)• Web: www.binarywave.com• Blog: www.sharepointcowboy.com• Twitter: @eshupps• Facebook: www.facebook.com/sharepointcowboy
    • Agenda• Infrastructure – Network – Servers – Databases Demonstrations• Configuration – Caching – Compression 10 – Throttling and Locks 8• Pages 6 – Customization 4 – Branding 2 Load Time – Lists• Instrumentation
    • Infrastructure
    • Network• Capacity• Load• Traffic Isolation – Web – Database – Service Applications – Search – Authentication• Indexing
    • Servers• Design to function – Heavy read operations require more web servers – Heavy write operations require increased SQL IOPS – Heavy services (i.e. Search) require additional application servers• Design to Locality – Global distribution with heavy write may require localized farms
    • Database Operations Search Security Trimming Workflow Content QueryIntensity Publishing Collaboration Social Client Access Browsing Frequency
    • Database CalculationsVariable Value Total Database Sizing# Documents 1,000,000 EstimateAverage Size 150 KB 864.4 GB# List Items 3,000,000# Versions 3 Formula: Database size = ((D × V) × S) + (10 KB × (L + (V × D))) Database Size Estimates Number of User ProfilesContent DB Size 486.5 GB 50,000Crawl 22.4 GBProperty 7.3 GBProfile 48.8 GBSync 30 GBAll other DB’s 269.5 GB
    • Application Databases• Small to moderate size• Moderate transactional volume Profile• Group on moderate PerformancePoint cost/performance disk• Analytics BCS – May be quite large PowerPivot – May require isolation App Registry – Reporting increases operational overhead Word Automation Analytics
    • Content Databases• Practical limit is 200GB – Max supported limit is 4TB*• Create separate databases for: – Site collections with large lists – Large numbers of subsites – Intensive read/write operations – Data isolation (security)• Consider amount of time it takes Content to backup/restore
    • Search Databases• Crawl databases can be extremely large• High index sensitivity Admin Properties• Heavy transactional volume• Isolate crawl and temp databases – Distribute across spindles and LUN’s Crawl• Highest performance disk
    • Database Management• Manually configure auto-growth settings• Defragment indexes on a regular basis• Limit content DB size per site collection• Assign disks based on size, volume and sensitivity• Isolate transaction logs• Implement regular backup schedule to reduce log file size• Enforce quotas
    • Configuration
    • SharePoint Caching Page Disk ObjectFirst request served Commonly from content File-system objects requested objects database, output cached by IIS stored in memorywritten to memory Subsequent requests for same Database objects Cross-site queriesresource read from not cached cached in memory memory
    • DEMOManaging Cache Settings
    • IIS Compression• Reduces size of files transmitted across the wire• Caches compressed content on disk• Configurable for various file types• Compression range from 0 - 9• Increases CPU utilization on WFE’s – Size hardware accordingly• Does not effect dynamic content retrieved from database
    • DEMOSetting Compression Levels
    • Throttling and Locks• SQL Server escalates row locks to table locks (> 5000)• Query throttling reduces the impact of any single request by limiting the amount of data queried• Throttling is configurable and can be altered for administrators and specific time periods• Bit rate throttling controls download speeds of large objects (video, Flash, Silverlight) – Dependent upon BLOB cache
    • DEMOResource Throttling
    • Pages
    • Page Controls• Navigation• Menus• Ribbon• Delegate• Security Trimming• Publishing Fields• Search• Layout• Hidden
    • Page Data Queries PageMaster Layout Navigation Menu Web Permissions Page Page Controls Options Parts File Database External System Data Sources
    • Page CustomizationsUncustomized Customized Cache
    • Test Results Average Performance Delta: ~10%0.10.080.060.040.02 0 1 2 3 4 5 6 7 8 9 10 Uncustomized Customized
    • DEMOCustomization
    • Branding• Start with a minimal master page• Minify and consolidate linked files – Reduce size and number of GET operations• Use image stitching (CSS sprites) on pages with a lot of small images to reduce number of requests• Store resources (style sheets, master pages, layout pages, images) on the PHYSICAL file system (i.e. /_layouts/) not the VIRTUAL file system (Style Library, Publishing Images) – Assets in libraries are stored in database – Easy for users to modify but reduce performance
    • Lists
    • List Items• Just because a list CAN hold millions of items doesn’t mean it SHOULD• All user content in all lists throughout entire site collection is stored in a single table in the content database – Consider query impact across site collection• Folders improve view performance NOT query performance• List view web parts are now XSLT based; however, large list displays may still require custom code
    • List Definitions• Rows – More than 5,000 rows in a list is “large” • Default throttle limit • Corresponds to SQL lock escalation triggers • Monitor locks if increasing throttle limit• Columns – More columns = more SQL rows – More SQL rows can slow down performance up to 35%• Storage – Use Remote Blob Storage to eliminate storage of large files within SQL – Not intended to increase query performance
    • Instrumentation
    • Developer Dashboard• Developer Dashboard provides metrics on object execution for individual pages• Displays code-level request data for events• Provides drill-down process isolation• Specifies related database queries• Identifies request allocations and control event offsets• Developers can implement monitoring scopes to display component performance data
    • Dashboard Example Total Page Execution Time Related Queries Control Events
    • DEMOUsing the DeveloperDashboard to Isolate Performance Issues
    • More InformationSharePoint Server 2010 Capacity Management: Software http://technet.microsoft.com/en-Boundaries and Limits us/library/cc262787.aspxCapacity Management and Sizing Overview for SharePoint http://technet.microsoft.com/en-Server 2010 us/library/ff758647.aspxCapacity Planning for SharePoint Server 2010 http://technet.microsoft.com/en- us/library/ff758645.aspxPerformance Testing for SharePoint Server 2010 http://technet.microsoft.com/en- us/library/ff758659.aspxStorage and SQL Server Capacity Planning and http://technet.microsoft.com/en-Configuration us/library/cc298801.aspxPerformance and Capacity Technical Case Studies http://technet.microsoft.com/en- us/library/cc261716.aspxMonitoring and Maintaining SharePoint Server 2010 http://technet.microsoft.com/en- us/library/ff758658.aspxPerformance Testing for SharePoint Server 2010 http://technet.microsoft.com/en- us/library/ff758659.aspx
    • Thank You for attending this session! Please fill in the evaluation form