FARM (Top)
SERVERS (WFE, AT, DT)
WEB APPLICATIONS (CA, SSP Admin, Content)
DATABASES (Config, Content, SSP, Search)
SITE COLLECTIONS (Portals, Team Sites, Blogs)
SITES (Blogs, Wikis, Team)
LISTS (Doc Libraries, Events, Pages, Discussions, Surveys)
ITEMS (Files, Items, contacts, images)
CONFIG DB: Servers, Web Apps (VServers), Solutions, Global Config at the Farm Level (Medium Demand)
CONTENT DBs: Site Collections, Sites, Lists, Pages, Docs, Web parts for each Web App (Low Demand)
SEARCH/SSP DB: Search, My Site, Profiles, BDC Config, Excel Calculation Services (Most Demand)
Top Performance killers:
-
Indexing / Crawling
-
Backup (SQL & Tape)
-
Profile Import
-
Misc Timer Jobs
-
Poor Storage Configuration
-
STSADM Backup/Restore
-
Large List Operations
-
Heavy user operation list Import/Write
-
Network latency
-
Inefficient Queries
| Scale Out | Scale Up |
| Add Servers | Add hard drive disks |
| More Servers, More Money, More Management | Complicates Design |
| Better Performance, Better Flexibility | Easier to manage, cheaper |
| more expensive, harder to manage | Design is critical, single point of failure |
| More flexible | more cost effective |
Highly Available/Disaster Recovery Scenarios
| Mirroring Within Farm | Mirroring/Log Shipping between Farms |
| Great combo HA/DR | allows long distance seperation |
| cheaper to implement | can protect against logical corruption |
| easier to manage | very flexible |
| requires closely located datacenter | more expensive |
| requires excellent network conditions | harder to setup and manage |
| not flexible | failover ??? |
| content corruptions is immediately replicated |
for best performance, do not exceed the following SharePoint/DB limits:
- DO NOT EXCEED 100GB – backup/restore maintenance
- use differential backup
- isolate large sites
- use multiple data files
- defrag regularly
- DO NOT EXCEED 2000 items per folder or view
- define limits on views
- use indexed columns
- SQL Memory RAM
- number and size of content dbs
- number of concurrent requests to SQL
- size and width of commonly used lists
- recommended 16GB and above
SharePoint 2010 databases – atleast 25 NEW dbs
FARM
- Config
- Admin Content
- Application Registry Service
- State Service
- Web Analytics Web Service
- WSS Usage
- ReportingDB
- Staging DB
SERVICES
- Search Service Application
- Crawlstore
- Search DB
- PropertyStore
- WSS Search
- SocialDB
- ProfileDB (SSP DB)
- SyncDB
- BDC_Service_DB
- Word Conversion Service Application
- Performance Point
- ManageMetadata
- Secure_Store_Service
CONTENT
- WSS_Content_GUID.
Thanks to Joel Oleston presentation on large scale deployments – performance review of SQL in SharePoint
Turlaps 