SharePoint 2013Performance optimization

Roger Haueter, ADVIS AG

we care about IT

Speaker

Microsoft Certified Solutions Expert: SharePointMicrosoft Certified Solutions Expert: Windows InfrastructureMicrosoft Certified IT Professional: Enterprise AdministratorMicrosoft Certified IT Professional: SharePoint 2010, Administrator

Community Leader of SharePoint Community Schweizhttp://www.sharepointcommunity.ch

Founder of SharePoint Community Mittellandhttp://www.sharepointmittelland.ch

Blogstechtask.comblog.advis.ch

Twitter @techtask

Facebook/techtask

Xing/Roger_Haueter

LinkedIn/rogerhaueter

Roger HaueterSharePoint Consultant

we care about IT

Definition of performance Performance optimization

• Clients• Network• Server• IIS• SQL• Storage• SharePoint

Agenda

we care about IT

Definition of performance

• End-user perspective• IT department perspective

we care about IT

End-user perspective

First page hit Subsequent page hits

Create a site, list or library

File upload (3 MB)

<5 seconds <3 seconds <5 seconds <5 seconds

we care about IT

IT department perspective

Latency Data throughput Processor / RAM Reliability

Software boundaries and limits for SharePoint 2013http://technet.microsoft.com/en-us/library/cc262787.aspx

we care about IT

Client performance optimization

• Important performance factors

we care about IT

Install latest updates

Client

Operating system Antivirus Microsoft Office Internet Explorer

Exclude files from real-time scanhttp://support.microsoft.com/kb/822158

Use newest Office version for best compatibility

Add your domain to «Local Intranet Zone», disable «Auto Detect Proxy Settings»

we care about IT

Network performance optimization

• Important performance factors

we care about IT

Between SharePoint and SQL servers

Network

Latency <1 ms Co-Location Number of NICs Traffic Isolation

Host all servers in the same data center

Use multiple network cards per server (teaming)

Configure a separate VLAN

we care about IT

Server

• Important performance factors

we care about IT

Choose«Best performance»http://www.techtask.com/?p=2126

Windows Server OS

Windows Server performance

options

Determine page file size

Use the proper power plan Create a SQL alias

Factor 1,5 of the server RAM. Ex: 8192 MB RAM x 1,5 = 12288 MB page filehttp://www.techtask.com/?p=2126

«High performance» instead of «Balanced»http://www.techtask.com/?p=2126

Create one for content and search on every SP Server (cliconfg.exe)http://www.techtask.com/?p=80

we care about IT

Spooler, AudioSrv, TabletInputService, WerSvc services

Windows Server OS

Stop / disable unused services

Disable loopback check

Load balancing != NLB Patching

on test servers or use BackConnectionHostNames in a productive environmenthttp://www.techtask.com/?p=1147

Use a hardware load balancer

Install latest OS and SharePoint updateshttp://www.techtask.com/?p=2767

we care about IT

Spread system, log files and index files on separate disks

Windows Server OS

Index and log files on separate disks Antivirus Reduce I/O Windows

Firewall

Exclude files from real-time scan http://support.microsoft.com/kb/952167

Spread system, log files and index files on separate disks

Manually define the SQL rules on the Windows Firewallhttp://www.techtask.com/?p=1937

we care about IT

Reduce loading time on first page hithttp://www.techtask.com/?p=2388

Internet Information Services (IIS)

Wake-up script Authentication Compression Blob Cache

Claims authentication with kerberos

For slow connections use compression(such as mobile phones)

Files are cached on the Web Front-end servers disks

we care about IT

SQL performance optimization

• Installation• Settings• Storage• Databases

we care about IT

Use a separate SQL instance on a cluster http://www.techtask.com/?p=2126

SQL installation

DedicatedSQL server

Named SQL instance

Latin1_General_CI_AS_KS_WS

Windows Authentication

Do not use the default instancehttp://www.techtask.com/?p=2126

Use the correct collationhttp://www.techtask.com/?p=1751

Use best practices

we care about IT

Pre-configure the model DB

SQL installation

Create databases with PowerShell

Dedicated search instance

Features and components Antivirus

Use a dedicated search instance if you have more than 10’000’000 items in the search index

Install only features and components you needhttp://www.techtask.com/?p=2126

Exclude data files, transaction logs and backup files from real-time scanhttp://www.techtask.com/?p=2126

we care about IT

Set min. and max. server memory (spare 3 GB for operating system)http://www.techtask.com/?p=2126

SQL settings

Server Memory Default Index Fill Factor = 80%

Activate backup compression

Max Degree of Parallelism

(MAXDOP) = 1

Maximum fill factor per indexhttp://www.techtask.com/?p=2126

It’s faster and needs less disks spacehttp://www.techtask.com/?p=2126

Serial execution of querieshttp://www.techtask.com/?p=2126

we care about IT

Use separate database volumeshttp://www.techtask.com/?p=2126

SQL storage

Use different LUNs RAID 10 NTFS allocation

unit size Sector alignment

Alternatively you can also use RAID 5 (lower perfmance)http://www.techtask.com/?p=2126

Set on 64Khttp://www.techtask.com/?p=2126

Best practice: 64Khttp://www.techtask.com/?p=2126

we care about IT

Data prioritization among faster disks (descending)• Temp DB data files• Temp DB logs• Content DB logs• Search DB data files• Content DB data files• Search DB logs• Weitere SharePoint data files• Weitere SharePoint logs

Separate transaction logs of search and content DBs

SQL storage

we care about IT

SQL Model DB settings

Pre-configure Initial sizeMDF

Initial sizeLDF Autogrowth

Use a valid assumption (for example 512 MB)

1/8 of the initial MDF file size

25-50% of the initial MDF/LDF file sizes, as a fix value in MB

Set meaningful values

we care about IT

25% of the biggest content DB

SQL TempDB settings

Initial size Data file sizeNumber of data

files = Number of processor cores

Autogrowth

Use the same size for all data files

Min. 4 / Max. 8Set T-Flag 1117http://www.techtask.com/?p=2126

10% of the assigned TempDB size, as a fix value in MB

we care about IT

Increase the database size to the size you expect in 12-24 monthshttp://www.techtask.com/?p=2126

SQL Content DB settings

Pre-grow Autogrowth in MB

Number of data files = Number of processor cores

Recovery model

Set the size in MBhttp://www.techtask.com/?p=2126

Min. 4 / Max. 8Set T-Flag 1117Use the same size for all data fileshttp://www.techtask.com/?p=2126

SimpleFull when using HA with log shipping or DB mirroringhttp://www.techtask.com/?p=2126

we care about IT

SharePoint performance optimization

• Architecture• Settings• Search• Caching• Performance killer

we care about IT

Avoid long-running backup and restore jobs

SharePoint architecture

Content DBs <200 GB

5’000 Site Collections

10 application pools

20 web applications

Maximum per content database

Maximum per Web Front-end server

Maximum per SharePoint farm

we care about IT

Set quotas on all web applications

SharePoint settings

Set quotasCertificate

revocation list checks

Authentication Wake-up script

Disable the CRL checks if the server has no internet connectionhttp://www.techtask.com/?p=1967

Performance (descending): Anonymous, Claims Auth, Kerberos, NTLM, Forms, ADFS

Sites are loading faster on first hithttp://www.techtask.com/?p=2388

we care about IT

Distribute the load on multiple crawl servers (loop on localhost in bigger environments)

SharePoint search

Number of search servers Throttling Incremental vs.

continuous crawl Content sources

Throttle crawling, adjust crawl scheduling

Continuous crawling needs more system ressources

Group by speed

we care about IT

<5% of RAM is used for newsfeeds, micro blogging, security trimming, FedAuth cookie etc.

SharePoint caching

Distributed cache Object cache Client cache Output cache

Configure cache users (SuperUser, SuperReader)

Websites with images, CSS, javascripts etc. are cached on the client

Caches site collections and subsites. Requires the publishing feature.

we care about IT

Ressource-intensive SharePoint service applications

Excel services Search Usage and health data collection

User profile service

application

we care about IT

SharePoint performance killer

Application pools recycle Crawl jobs Backup jobs Large list

operations

we care about IT

Test the performance immediately prior the go-live

SharePoint load test

Before the go-live Productive farmSimulate the

expected amount of users

Visual Studio team system

or on an equivalent pre-production farm

Define goals: Loading time should be less than 3 secs with 5’000 active users

Available in Visual Studio Ultimate 2013. Or use the SP 2010 Admin Toolkit v2.0

we care about IT

TechTask // SharePoint Blog (Wake-up script & SQL best practices)http://www.techtask.com

ADVIS Bloghttp://blog.advis.ch

SharePoint Community Mittelland (SPCM)http://www.sharepointmittelland.ch

Slides of the SPCM presentation «Pimp my SharePoint»http://is.gd/Cc2MXJ

Further information

we care about IT

Q & A