Microsoft Sharepoint Products and Technologies Resource Kit eBook

■ Divisional portal site access
■ Windows SharePoint Services site usage
■ My Site usage
Chapter 9: Capacity Planning 213
The following example illustrates how to estimate required throughput for a
divisional portal site component of the total workload. Table 9-1 shows sample characteristics
representing a divisional portal site supporting approximately 10,000
users. This is a reasonably diverse workforce group, using a mix of common portal
site functions and a small percentage of complex functions. Most users typically
access the site through simple activities such as locating information by browsing
categories, searching for documents that match their needs, or reading divisional
news or announcements on the Home page.
Note Document collaboration functions (including document check-in and
document upload) are weighted differently than other functions. These more
complex activities take several steps to accomplish. Therefore, they should
be rated as three times as intense as other functions.
Table 9-1 Characteristics Representing a Divisional Portal Site
Characteristic Value
Number of potential users 10,000
Percent of active users per day 80
Number of common operations per active user per day 32 × (weight = 1.0) = 32
Number of complex operations per active user per day + 8 × (weight = 3.0) = 24
Number of operations per active user per day 56
Number of hours per day 12
Peak factor 4
10000 users × 80 % usage × 56 operations × 4 peak = 41.48 ops/sec
360000 × 12 hours per day
As shown, these characteristics yield a predicted peak throughput requirement
of about 42 operations per second. To run just this portal site, a medium server farm
with two load-balanced front-end Web servers, an indexing server, and a server
running the SQL component would be needed. A rough estimate for performance
is each 1 GHz of processing power in the front-end servers can support 9 to 10