12. Page
First request served
from content database,
output written to
memory
Subsequent requests
for same resource read
from memory
Disk
File-system objects
cached by IIS
Database objects not
cached
Object
Commonly requested
objects stored in
memory
Cross-site queries
cached in memory
17. Throttling Rules
Rule
1
Rule
2
Rule
3
Execution Group 0
Rule
1
Rule
2
Rule
3
Execution Group 1
Rule
5
Rule
6
Rule
7
Execution Group 3
Rule
8
Rule
9
Rule
0
Machine Pool 1
Server
1
Server
2
Server
3
Machine Pool 2
Server
4
Server
5
Server
6
ERIC
Physical hardware resources, network connectivity, disk size and speed, location of data files, configuration of shared storage—all aspects must be taken into consideration based on the size of the farm and the projected amount of data.
SharePoint is both read and write intensive, so separating the I/O operations onto separate disks prevents excessive thrashing and cache hits
Suggest - one set of disks for search databases, one for temporary databases, and still another for content databases
Pre-size the databases up to the maximum recommended
size (200GB) if space is available and set autogrowth to a fixed size (e.g. 10MB or 20MB). This will prevent SQL from expanding databases unnecessarily and insure that growth happens in a manageable fashion
Defragment Database Indexes
Indexes can become fragmented over time as new INSERT, DELETE and UPDATE operations are performed
Plan for regular maintenance operations which include index defragmentation