View
298
Download
0
Category
Tags:
Preview:
Citation preview
20th June 2015Florence
20th June 2015Florence
Introduction to Performance Optimization for SharePoint 2013 and Office 365
Gokan Ozcifci@gokanozcifci
Apologies for accentWith Turkish blood, Dutch educated and a French speaking guy..
Gokan Ozcifci
Neoxy Consultancy
gokan@neoxy.be
@gokanozcifci
facebook.gokan.ms
linkedin.gokan.ms
Gokan (for Business) is a Microsoft SharePoint MVP. MCT. MCC. I do sometimes things with SharePoint. Opinions are my own.
Contact details:
#SPSFlorence2015
A Huge “Thank You!” To Our Sponsors …
What about this session?What does performance really mean?
Provide some insights and tips about Performance improvements.
TechNet/MSDN is not always your answer.
Other platforms also matters and why?
Everybody has his own experience.
85 – 95% you already know this.
90/10 (On-Premises – Cloud)
The difference in vision
Azure & O365
Exchange & Lync +
Voice
Cloud Ready
Windows Server
Authentication and
Authorization
System Center 2012
ITSM / ITIL
Migrations
Integrations
OTB Workflows Dashboards
Home made
applications
Portals and Intranets
ReportsOffice Pack
Infrastructure Business Productivities.
The Microsoft Expertise. A real added value.
The difference in vision
Infrastructure Business Productivities.
The Microsoft Expertise. A real added value.
Understand SharePoint
SharePoint covers a huge set of individual technologies under the SharePoint Platform umbrella
Application DomainActive DirectorySQL ServerOffice Web Apps Server…
It requires time, patience and experience as it’s continuously changingKnow when to use OOTB vs Custom ComponentsKnow your users
Understand SharePointNew Service Applications (Machine Translation)Offloaded Services: Yammer, OneDrive for Business, Office Web Apps, Workflow Manager…Improved Service Applications (Fast)Not UI Bindended Services to be managed with PoSH (Subscription Management)Re-architected Service Applications (Search & OWA)
Different release scheduleOWA can be used for other platforms like Lync, Exchange, …
SharePoint is down!
What is really down?
SharePoint is more than a List, Library or site.
For the business, if …
For the business, if …
First page hit
Subsequent page hits
Create a site,
list or library
File upload (3 MB)
< 5 Seconds < 3 Seconds < 5 Seconds < 5 Seconds
N-Tier, N-Layer
#1 Train your UsersSet measurable goalsDraw a RoadmapDefine and pick some pilotsChoose your Site Content and Site OwnersTrain your users
… again… and again
Technical Improvements
Fine-tuning Client Side
Operating System. Install Latest updates. At least Windows 7. Silverlight 3.
Office 2013.
Antivirus. Exclude files from real-time scan for Enterprise computers:
Turn off scanning:Windows Update or Automatic
Update related filesWindows Security files
Group Policy related filesSYSVOL files DFS and DHCP files
Fine-tuning Client Side
Microsoft Office. Use the newest Office Version for best compatibility
Microsoft Office 2010 with Service Pack 2 With KB 2553248
Microsoft Office 2007 with Service Pack 2 With KB 2583910
Microsoft Office for Mac 2011 with Service Pack 1
Microsoft Office 2008 for Mac version 12.2.9
Support ends April 9, 2013.
Internet Explorer. SharePoint 2013 supports several commonly used web browsers, such as
Explorer, Google Chrome, Mozilla Firefox and Apple Safari. However, certain web browsers could cause some SharePoint 2013 functionality to be downgraded, limited, or available only through alternative steps.
Supported: Internet Explorer 11, Internet Explorer 10, Internet Explorer 9, Internet Explorer 8
Fine-tuning NetworkLatency between SharePoint Server and SQL Server should be less than 1msHost all the servers in the same datacenter. /!\ If the datacenter has a problem, your SharePoint farm can be down /!\Don’t use Network Load Balancing (NLB), but a real load balancer like F5
VLANs can provide significant throughput gains: • VMs on the same VLAN can communicate through the
virtual switch, network traffic is faster because it does not have to use the physical network adapter.
• As it’s software-based, a virtual machine can easily be moved between hosts and still keeps its network configuration.
Fine-tuning Windows Server
Windows Server performance options
Computer > Properties > Advanced system settings > Performance > Settings > Visual Effects
Fine-tuning Windows Server
Determine page file size
Factor 1,5 of the server RAM. Ex:
8192 MB RAM x 1,5 = 12288 MB page file
Computer > Properties > Advanced system settings > Performance > Settings > Advanced > Virtual Memory > Settings
Fine-tuning Windows Server
Use the proper power plan
High Performance
Start > Control Panel > Power Options
Fine-tuning Windows Server
Stop / disable unused services
Spooler
AudioSrv
TabletInputService
WerSvc services
Fine-tuning Windows Server
Loopback check
On test servers or use BackConnectionHostNames in a Production environment
Fine-tuning Windows Server
Patching
Install latest OS and SharePoint updates
(If necessary!)
Fine-tuning Windows Server
SQL Alias
cliconfg.exe
• Operational tasks
• maintenance is easier.
• Upgrades
• Downgrades
Fine-tuning Windows Server
Windows Firewall
Manually define the SQL rules on the Windows Firewall
• 1433 (TCP)
• 1434 (UDP)
Fine-tuning Windows Server
Antivirus
Exclude files from real-time scan Drive:\Program Files\Common Files\Microsoft Shared\Web Server Extensions
Drive:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\Logs
Drive:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\Data\Applications
Fine-tuning Windows Server
Reduce I/O
System, Log and Index files should be on separate disks.
• C: System
• G: Index
• H: Logs
Fine-tuning SQL Server
Physical vs Virtual• Easier to scale up & down
• Hyper-V Cluster in Windows Server 2012 will allow you to easily move machines between hosts when there are updates or problems
• Can be easier to recover at DR. You're not in the position to reload the OS, reload SQL Server
Fine-tuning SQL Server
Small Farm Deployment (0-500GB of Data)
Medium Farm Deployment (501-1TB of data)
Large Farm Deployment (1-2TB of Data)
Very Large Farm Deployment (2-5 TB of Data)
Special Cases
RAM 8 16 32 64 64+
CPU 4 4 8 8 8
Fine-tuning SQL Server
Dedicated SQL Server For optimal performance when operating server farms, we recommend that you install SQL Server 2008 R2 with SP1 and SQL Server 2012 on a dedicated server that is not running other roles of farm and n 'not host databases for other applications
Dedicated Instance
Fine-tuning SQL Server
Collation: Latin1_General_CI_AS_KS_WS
Cannot be changed after wise
Windows
AuthenticationNo Mixed Mode
Fine-tuning SQL Server
Create your Databases with PoSH!
Fine-tuning SQL Server
• Use a dedicated search instance > 10’000’000 items
• Antivirus: Exclude data files, transaction logs and backup files from real-time scan
• Install only features and components you need. SharePoint only requires: Database Engine Services
• Do not enable Statistics
Fine-tuning SQL Server
Set min. and max. Server• /!\ Total amount memory x 0,80 /!\ The default value of SQL Server for
Maximum Memory is : 2147483647 MB
Maximum fill factor per index (80%)
Activate backup compression• It’s faster and needs less disks space
Max Degree of Parallelism (MAXDOP) = 1
• Prerequisite for SharePoint 2013
Fine-tuning SQL Server
NFTS Allocation Unit Size: 64K
• SQL reads and writes 64K at a time, but your disk allows only 4K by default. This change alone may show you up to 30% improvement in speed.
• “chkdsk c:”
• Cannot be changed expect formatting
Fine-tuning SQL Server
Model DatabaseEvery time a new Content Database is
created by SharePoint to store your Web Application, SQL uses the information in the Model Database to create it.
Initial Size:This will help performance, as SQL won’t have to constantly ask for more space to store
data.
Auto Growth:Do not keep the default value which is 1 MB. When a document of 5 MB is uploaded,
it means there are 5 Autogrowth which are activated. In fact, there are 5 allocations of space which must slow your system.
Moreover, your uploaded document will be fragmented across your different data files. This configuration will decrease your performance a second time.
Fine-tuning SQL Server
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
• SharePoint data files
• SharePoint logs
Fine-tuning SharePoint Server (architecture)
• Content Databases shouldn’t be more than 200GB• Backup / Restore
• Operational tasks
• 5000 Site collections per Content Database
• 10 Application Pools (can be extended depending hardware)
• 20 web Applications per SharePoint Farm
• Don’t use the Product Configuration Wizard
Fine-tuning SharePoint Server (settings)
• Set Quotas on all Web Applications
• Disable Certificate Revocation List
• Authentication
• Anonymous, Claims, Kerberos, NTLM, Forms, ADFS
• Wake-Up
• Only extend if you have a different authentication protocol.
Fine-tuning SharePoint Server (Search)
• Distribute the load on multiple crawl servers
• Throttle crawling, adjust crawling schedule
• Incremental vs continuous crawl
• Content sources
• Group by
Fine-tuning SharePoint Server (Search)
Fine-tuning SharePoint Server caching
• Distributed Cache
• Object Cache (SuperUser, SuperReader)
• BLOB Cache
• Output cache (caches SC, Publishing features)
Fine-tuning SharePoint Server (Resource-intensive Service Applications)
• Excel Service Application
• Search Service Application
• Usage and Health Data collection
• User Profile Service Application
Fine-tuning SharePoint Server (Performance killer)
• Application Pool Recycle && IISReset
• Crawl Jobs (continuous crawl)
• Backup Jobs
• Large list operations
Fine-tuning PowerShell
• Try to avoid –Force
Use the Force switch only for fixing broken deployments of SharePoint Packages. Not only it makes SharePoint stop affected Application Pools but also it prevents you from seeing errors should there be any.
Fine-tuning PowerShell
• Scope your Solutions with PoSH
• When a solution is deployed globally, all SharePoint application pools, including Central Administration’s, are recycled automatically. This can be good and bad. This is good because any GAC installed DLL that has been upgraded needs to be reloaded. This can be bad though with regards to the availability of your entire SharePoint Farm.
Fine-tuning Office 365
1,000ms
5,000ms
The slowest 1% of pages in SharePoint online take more
than 5,000ms to load75% of SharePoint Online pages load in less than 1,000ms
Fine-tuning Office 365
Internet peering and routing
Customer Internet connection
Microsoft network
Microsoft edge nodes
Content delivery network
Serverworkloads
Rich clientapplications
Why SharePoint pages get slow…
Server
Browser
Network
Complex pagesToo many web parts
Large payloadToo many filesLarge distance to server
Complex pagesBusy computerSmall cache
Server
Expensive server interactionsFront end cache misses
Network
MicrosoftNetwork
Internet
ISP
CDN
SharePoint Online bandwidth usage
• Web Based File upload and download
• Sync client is the main bandwidth user
• OneDrive for Business initial sync traffic
SharePoint Online ImagesKeep them small
• Compress images before uploading them to SharePoint
Reduce download sizes• Minify all JavaScript and CSS assets
Reduce the number of HTTP requests• Bundle static assets together to reduce HTTP
requests
• Deliver static content via CDN’s if possible
• Parallelize downloads across multiple hostnames
Troubleshooting performance process
Network Capture tool
• Netmon
• WireShark
• TCPDump
• Microsoft Message Analyzer
Application Level tools
• HTTPWatch
• Fiddler
Summary
• Performance -, it depends
• Other platforms also matters
• SharePoint is fast, but depends many about others
• You can improve, improve and improve
QUESTIONS&
ANSWERS
Thank You!
Please fill the feedback form!
20th June 2015Florence
Recommended