Microsoft SharePoint Server 2010 Technical Case Study: … · 2010-09-19 · Microsoft SharePoint Server 2010 Technical Case Study: Enterprise Intranet Publishing Environment This
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Microsoft SharePoint Server 2010 Technical Case Study: Enterprise Intranet Publishing Environment This document is provided “as-is”. Information and views expressed in this document, including URL and other Internet
Web site references, may change without notice. You bear the risk of using it.
Some examples depicted herein are provided for illustration only and are fictitious. No real association or connection is
intended or should be inferred.
This document does not provide you with any legal rights to any intellectual property in any Microsoft product. You may
copy and use this document for your internal, reference purposes.
Configuration............................................................................................................................................... 9 Workload ........................................................................................................................................................ 10 Dataset ........................................................................................................................................................... 10 Health and Performance Data ............................................................................................................................ 11
General Counters ....................................................................................................................................... 11
Workload This section describes the workload, which is the demand on the farm, including 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
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, including 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 specific to the case study environment.
General Counters 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
17,77% 15,88%
23,87% 22,70%
0%
10%
20%
30%
40%
50%
60%
70%
80%
90%
100%
Front-end Web Server Database Server
Average CPU Utilization
Typical
Peak
In this document, latency is divided into four categories. The 50
th 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 server spikiness. It means that 95% of requests are served within that response time, and thus 5% of the requests experience slower response times.
Database counters When interpreting database statistics for this enterprise publishing environment, note that the majority of visitors have