Enterprise intranet publishing environment technical case study (SharePoint Server 2010)
Applies to: SharePoint Server 2010
This document describes a specific deployment of Microsoft SharePoint Server 2010. It includes the following:
Technical case study environment specifications, such as hardware, farm topology and configuration
The workload that includes the number, and types, of users or clients, and environment usage characteristics
Technical case study farm dataset that includes database contents and Search indexes
Health and performance data that is specific to the environment
In this article:
Prerequisite information
Introduction to this environment
Specifications
Workload
Dataset
Health and Performance Data
Prerequisite information
Before reading this document, make sure that you understand the key concepts behind SharePoint Server 2010 capacity management. The following documentation will help you learn about the recommended approach to capacity management and provide context for helping you understand how to make effective use of the information in this document, and also define the terms used throughout this document.
For more conceptual information about performance and capacity that you might find valuable in understanding the context of the data in this technical case study, see the following documents:
Capacity management and sizing overview for SharePoint Server 2010
SharePoint Server 2010 capacity management: Software boundaries and limits
Introduction to this environment
This white paper describes an actual SharePoint Server 2010 environment at Microsoft. Use this document to compare with your planned workload and usage characteristics. If your planned design is similar, you can use the deployment described here as a starting point for your own installation.
This document includes the following:
Specifications, which include hardware, topology and configuration
Workload, which is the demand on the farm that includes the number of users, and the usage characteristics
Dataset that includes database sizes
Health and performance data that is specific to the environment
This document is part of a series of Performance and capacity technical case studies (SharePoint Server 2010) about SharePoint environments at Microsoft.
.gif "Diagram shows environment in context at Microsoft")
The SharePoint Server 2010 environment described in this document is a production environment at a large, geographically distributed company. Employees view various content, such as news, technical articles, employee profiles, documentation, and training resources. Employees also use this environment to perform search queries against all the SharePoint environments within the company. Employees receive daily e-mails with links to articles on the environment and many employees set this environment as their browser home page.
As many as 48,000 unique users visit the environment on a busy day, generating up to 345 requests per second (RPS) during peak hours. Because this is an intranet site, all users are authenticated. Although content is published using a single environment author-in-place model, the environment’s publishing procedure specifies that all draft content is published at a single time during the night in off-peak hours.
The information that is provided in this document reflects the enterprise intranet publishing environment on a typical day.
Specifications
This section provides detailed information about the hardware, software, topology, and configuration of the case-study environment.
Hardware
This section provides details about the server computers that were used in this environment.
Note
This environment is scaled to accommodate pre-release builds of SharePoint Server 2010 and other products. Hence, the hardware deployed has bigger capacity than necessary to serve the demand typically experienced by this environment. This hardware is described only to provide additional context for this environment and serve as a starting point for similar environments.
It is important to conduct your own capacity management based on your planned workload and usage characteristics. For more information about the capacity management process, see Capacity management and sizing overview for SharePoint Server 2010.
Web Servers
There are four Web servers in the farm, each with identical hardware. Three serve content, and the fourth is a dedicated search crawl target.
| Web Server | WFE1-4 |
|---|---|
Processor(s) |
2 quad core @ 2.33 GHz |
RAM |
32 GB |
Operating system |
Windows Server 2008, 64 bit |
Size of the SharePoint drive |
300 GB |
Number of network adapters |
2 |
Network adapter speed |
1 Gigabit |
Authentication |
Windows NTLM |
Load balancer type |
Hardware load balancing |
Software version |
SharePoint Server 2010 (pre-release version) |
Services running locally |
Central Administration Microsoft SharePoint Foundation Incoming E-Mail Microsoft SharePoint Foundation Web Application Microsoft SharePoint Foundation Workflow Timer Service Search Query and Site Settings Service SharePoint Server Search |
Services consumed from a federated services farm |
User Profile Service Web Analytics Web Service Business Data Connectivity Service Managed Metadata Web Service |
Application Server
There are no application servers in the farm. Local services are hosted on the Web servers. Other services are consumed from a federated services farm.
Database Servers
There is a SQL cluster with two database servers, each with identical hardware. One of the servers is active and the other is passive for redundancy.
| Database Server | DB1-2 |
|---|---|
Processor(s) |
4 quad core @ 2.4 GHz |
RAM |
32 GB |
Operating system |
Windows Server 2008, 64 bit |
Storage and geometry |
(1.25 TB * 6) + 3 TB Disk 1-4: SQL Data Disk 5: Logs Disk 6: TempDB |
Number of network adapters |
2 |
Network adapter speed |
1 Gigabit |
Authentication |
Windows NTLM |
Software version |
SQL Server 2008 |
Topology
The following diagram shows the topology for this farm.
.gif "Farm topology diagram for this environment")
Configuration
The following table enumerates settings that were changed that affect performance or capacity in the environment.
| Setting | Value | Notes |
|---|---|---|
Site Collection Administration: Site collection output cache |
On |
Enabling the output cache improves server efficiency by reducing calls to the database for data that is frequently requested. |
Site collection cache profile (select) |
Intranet (Collaboration Site) |
“Allow writers to view cached content” is checked, bypassing the ordinary behavior of not letting people with edit permissions to have their pages cached. |
Object Cache (Off | n MB) |
On – 500 MB |
The default is 100 MB. Increasing this setting enables additional data to be stored in the front-end Web server memory. |
Usage Service: Trace Log – days to store log files (default: 14 days) |
5 days |
The default is 14 days. Lowering this setting can save disk space on the server where the log files are stored. |
Query Logging Threshold: Microsoft SharePoint Foundation Database – configure QueryLoggingThreshold to 1 second |
1 second |
The default is 5 seconds. Lowering this setting can save bandwidth and CPU on the database server. |
Database Server – Default Instance: Max degree of parallelism |
1 |
The default is 0. To ensure optimal performance, we strongly recommend that you set max degree of parallelism to 1 for database servers that host SharePoint Server 2010 databases. For more information about how to set max degree of parallelism, see max degree of parallelism Option(https://go.microsoft.com/fwlink/p/?LinkId=189030). |
Workload
This section describes the workload, which is the demand on the farm that includes the number of users, and the usage characteristics.
| Workload Characteristics | Value |
|---|---|
Average Requests per Second (RPS) |
100 |
Average RPS at peak time (11 AM-3 PM) |
226 |
Total number of unique users per day |
33,580 |
Average concurrent users |
172 |
Maximum concurrent users |
376 |
Total # of requests per day |
3,800,000 |
This table shows the number of requests for each user agent.
| User Agent | Requests | Percentage of Total |
|---|---|---|
Browser |
3,261,563 |
97.09% |
DAV |
2,418 |
0.07% |
Search (crawl) |
92,322 |
2.75% |
OneNote |
1,628 |
0.05% |
Outlook |
961 |
0.03% |
Word |
449 |
0.01% |
Dataset
This section describes the case study farm dataset that includes database sizes and Search indexes.
| Dataset Characteristics | Value |
|---|---|
Database size (combined) |
49.9 GB |
BLOB size |
22.2 GB |
Number of content databases |
3 |
Number of Web applications |
3 |
Number of site collections |
4 |
Number of sites |
797 |
Search index size (number of items) |
275,000 |
Health and Performance Data
This section provides health and performance data that is specific to the case study environment.
General Counters
| Metric | Value |
|---|---|
Availability (uptime) |
99.95% |
Failure Rate |
0.05% |
Average memory used |
1.08 GB |
Maximum memory used |
2.60 GB |
Search Crawl % of Traffic (Search client requests / total requests) |
6% |
ASP.NET Requests Queued |
0.00 |
The following charts show the average CPU utilization and latency for this environment.
.gif "Chart showing average CPU utilization")
.gif "Chart showing latency in this environment")
In this document, latency is divided into four categories. The 50th percentile latency is typically used to measure the server’s responsiveness. It means that half of the requests are served within that response time. The 95th percentile latency is typically used to measure spikes in server response times. It means that 95% of requests are served within that response time, and therefore, 5% of the requests experience slower response times.
Database Counters
When interpreting database statistics for this enterprise publishing environment, be aware that most of the visitors have read-only permissions.
| Metric | Value |
|---|---|
Read/Write Ratio (IO Per Database) |
99.999 : 0.001 |
Average Disk queue length |
0.35 |
Disk Queue Length: Reads |
34 |
Disk Queue Length: Writes |
2.5 |
Disk Reads/sec |
131.33 |
Disk Writes/sec |
278.33 |
SQL Compilations/second |
2.36 |
SQL Re-compilations/second |
94.80 |
SQL Locks: Average Wait Time |
0 ms |
SQL Locks: Lock Wait Time |
0 ms |
SQL Locks: Deadlocks Per Second |
0 |
SQL Latches: Average Wait Time |
0.25 ms |
SQL Cache Hit Ratio |
>99% |
See Also
Other Resources
Resource Center: Capacity Management for SharePoint Server 2010