S TRESS TESTING RESULTS Performance has been tested for each of the key administration scenarios, and the maximum allowed number of client computers, which an Administration Server can serve within the specified time, has been identified. It is not recommended to use time intervals greater than one hour for key administration operations servicing all clients therefore, the data provided below cover the service intervals from 15 minutes to one hour. The following hardware configurations of the Administration Server were used for testing single-processor system (dual- core Intel Core Duo E with operating frequency 3.00 GHz, 4 GB RAM, HDD SATA 300 GB dual-processor system (two 4- core processors Intel Xeon™ with operating frequency 3.16 GHz, 6 GB RAM, HDD SCSI 200 GB. The Microsoft SQL 2005 database server was installed on the same computer as the Administration Server. The testing was performed in the 1000 Mbit/s Ethernet network. To perform the stress testing of Kaspersky Administration Kit 8.0, the following key administrative operations were selected Connection of client to Administration Server without synchronization (on page 107 ). This scenario imitates the "idle" state of the administration system when the Administration Server maintains periodic connections of the client computers without data synchronization. The Administration Server updates its database to register information about the last client connection to the Server, but no data is changed on the client computer. Connection of client computer to Administration Server with synchronization (see section "Connection of client to Administration Server with synchronization" on page 107 ). This scenario imitates the state when a policy or a group task is modified on the Administration Server and the client computer synchronizes its copy of the data with the Administration Server data when it connects to the Administration Server. Regular database updates (on page 108 ). This scenario imitates the situation when client computers update databases from the Administration Server using the Network Agent. Processing of events on client computers by the Administration Server (on page 105 ). This scenario imitates the state when client computers connect to the Administration Server and transfer events to it, for which information is registered in the Administration Server database.