Determine capacity requirements
WSUS 3.0 SP2 hardware and database requirements are mainly driven by the following factors:
Number of client computers in your organization.
Client computer synchronization frequency.
Number of languages in which updates are approved.
Single server or Network Load Balancing (NLB) configuration with two front end servers and a single powerful back end server. NLB is not a failover configuration.
The following sections provide hardware requirements and supported capacity information.
Minimum Hardware Requirements
These minimum server hardware and database configuration requirements apply to all installations of WSUS 3.0 SP2.
CPU – Minimum 1 GHz, 1.5 GHz or faster is recommended
Graphics card – 16 MB hardware accelerated PCI/AGP video card capable of 1-24*86*16bpp or more
RAM – Minimum 1 GB, 2 GB or more is recommended
Page file – at least 1.5 times physical memory
I/O subsystem – Fast ATA/IDE 100 hard disk or equivalent SCSI drives
Network adapter – Minimum 10 MB, 100 MB or more is recommended
Both the system partition and the partition on which you install WSUS 3.0 SP2 must be formatted with the NTFS file system
Minimum 1 GB of free space on the system partition
Minimum 2 GB of free space on the volume on which database files will be stored
Minimum 20 GB of free space on the volume on which content is stored, 30 GB is recommended
Notice that WSUS 3.0 SP2 cannot be installed on compressed drives.
Supported Capacity by Configuration
Additional hardware and database requirements depend on your how your organization implements WSUS 3.0 SP2 and your performance expectations. The following table shows performance data for the maximum number of supported clients for a single server implementation. The table includes test specifications and results that were achieved in the Microsoft test lab. You can use this data as a guideline to develop your own test scenarios and to make your hardware and software decisions.
Be aware that your organization’s performance results may vary if you choose to use different hardware; however, the maximum supported capacity figures do not change. That is, if you use a higher performance server than indicated in the table that follows, there may be an increase in the number of client synchronizations per second. However, there is no increase in the maximum number of supported clients for the configuration.
Sample Configuration and Maximum Supported Capacity
|Configuration||Maximum Supported Capacity||Hardware and Software||Client Synchronizations and Updates|
|Single server, non-NLB||100,000 clients||Hardware: Intel Core 2 Quad CPU Q6600, 2.40 GHz, 4GB RAM Software: Win2K3 Standard x64 SP2||Delta sync at 7 hour frequency Avg. requests per client: 10 Transaction rate: 6 clients per second|
Transaction rate is defined as the time that is required to service a single client, and includes multiple requests.
Performance testing was done by using delta sync requests. Be aware that an initial request to the server (a full sync) will generate a server CPU spike, as the server must build up its internal caches.
If WSUS clients synchronize with the server more frequently than is shown in the table, there will be a corresponding increment in the server load. For example, if clients synchronize every 4 hours in an NLB configuration, the load will be two times as much as an 8 hour synchronization frequency. Be aware that the Group Policy setting that specifies the number of hours that Windows uses to determine how long to wait before checking for available updates automatically staggers the requests to the server. The exact wait time is determined by using the hours specified minus zero to 20 percent of the hours specified. For example, if this policy is used to specify a 20 hour detection frequency, all clients to which this policy is applied will check for updates anywhere between 16 and 20 hours. Requests are processed first-in, first-out. If the number of concurrent sync requests exceeds capacity, they are held in the IIS queue until they can be processed.
Increasing the number of languages will also increase the server load. Updating in five languages, instead of one language will approximately double the size of the content directory.
Using the WSUS Admin console to run reports during the client sync process had no noticeable effect on performance.