1. SharePoint Solutions Architect, Protiviti
Practical tools and techniques for architecting and maintaining high performing SharePoint environments
Doug Hemminger
SharePoint Solutions Architect, Protiviti

2. Chicago About Me Contact Me
I am a Chicago-based Microsoft SharePoint Server MVP and a SharePoint Solution Architect for Protiviti
Contact Me
Blog:

3. Agenda Database Planning Performance Search Full Crawl
Continuous Crawl
Caching
Developer Dashboard

4. The evolution of file storage
Microsoft SharePoint
6/1/2018
The evolution of file storage
© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

5. Database – Planning and Performance

6. Database - Planning Use a dedicated server for SQL server
Collation = Latin1_General_CI_AS_KS_WS
Max Degree of Parallelism = 1
Do not enable auto-create statistics on a server that hosts SQL Server and SharePoint
Use a SQL Server alias to simplify moving the database in the future

7. Database - Planning Allocate 2 GB for the Configuration database
Allocate 1 GB for the Central Administration content database.
Unless using mirroring or Always On, change the recovery model for the databases list above from full to simple.
Use full recovery model in combination with appropriate backup strategy for all other databases.
Increase Autogrowth Settings (Use MB Not %)

8. Database - Planning
NTFS Allocation Unit Size should be 64 KB (8 8KB Pages = 1 Extent)
Priority (Fastest to Slowest Drive)
(Fastest) Tempdb Data and Transaction Log Files
Content and Search Database Transaction Log Files
Search Database Data Files
(Slowest) Content Database Data Files

9. Database - Planning
Size your databases to what you expect them to roughly grow to in 1-2 years.
Database size = ((D × V) × S) + (10 KB × (L + (V × D)))
D = Number of documents
V = Number of non-current version
S = Average size of each document
L = Number of list items (3 times the number of documents)

10. Database - Planning
200 GB Database size limit for collaboration databases
100 GB maximum for each site collection
Generally a mix of read and write operations
Up to 16 TB limit for records and archival databases
2 TB limit for each site collection
Generally only minimal read operations

11. Database - Performance
IOPS (Input/Output Operations Per Second)
Disk sub-system performance of 0.25 IOPS per GB to 2 IOPS per GB is recommended for optimal performance
For example, 100 GB Content DB should be on a disk that supports 25 to 200 IOPS. If you have 8 Content DBs of that size sharing a disk, you would plan for 200 – 1600 IOPS

12. Database Performance
Higher RPS (Requests Per Second) correlate to higher IOPS.

13. Database - Performance
SQLIO: Use to simulate and test Read and Write I/O patterns
SQLIOSIM: Use to test IOPS under load on an installed farm

14. Demo

15. Search

16. Search Database Scaling Disk IOPS Disk size 10M items 100M items Crawl
One DB per 20M items
SQL IOPS: 10 per 1 DPS
Medium/High
Medium
15GB
2GB log
110GB
50GB log
Link
One DB per 60M items
SQL IOPS: 10 per 1M items
10GB
0.1GB log
80GB
5GB log
Analytics Reporting
Split when reaching GB
Usage dependent
Search Administration
One DB
Low
0.4GB
1GB log
1GB data

17. Search
How long does a full crawl take on 20 million documents that exist on a disk subsystem with 500 IOPS
Example: 500 IOPS = 50 documents per second
20,000,000/50 = 400,000 seconds
400,000 seconds = 111 hours

18. Search – Continuous Crawl

19. Demo

20. Caching
Blob Cache - controls the caching for binary large objects (BLOBs), such as frequently used image, audio, and video files.
Output cache - Stores the rendered output of a page.
Object cache - stores objects such as lists and libraries, site settings, and page layouts in memory on the front-end web server.

21. Demo

23. Developer Dashboard
The Developer Dashboard contains an extensible mechanism for measuring various performance counters at various scopes.

24. Demo

25. Resources
Title
Url
Storage and SQL Server capacity planning and configuration (SharePoint Server 2013)
SQLIO Disk Subsystem Benchmark Tool.
How to use the SQLIOSim utility to simulate SQL Server activity on a disk subsystem.
Performance and capacity test results and recommendations (SharePoint Server 2013)
Tuning SQL Server 2012 for SharePoint 2013
Software Boundaries and Limits for SharePoint 2013
Best Practices for SQL Server in a SharePoint Server Farm

26. Please fill out a session survey for the HSPUG Technical presentation
Scan the QR code to the right or type bit.ly/hspugtech1411
If you submit a survey, you are eligible for an extra prize drawing!

27. Thank You!