Compaq 307560-001 Performance Analysis and Capacity Planning for Microsoft Sit - Page 19

operating system: Windows NT Server 4.0 with Service Pack 3. The SUT also had the TCP/IP

Page 19 highlights

WHITE PAPER (cont.) 1...9 Figure 6 shows the test lab configuration used for the ProLiant 7000 testing. The number of client systems and networks was also determined by experimentation until the CPUs were 100% utilized. Table 18 shows the actual number of client systems used and the configurations for each test. There were always two networks used in the ProLiant 7000 tests. Table18: ProLiant 7000 Test Lab Configuration Test # of Client Systems ILS Connect 8 ILS Add 4 ILS Direct Lookup 8 All PS Tests 3 # of Simulated Users and Worker Threads per Client System 50 20 50 11 Each of the PC client systems ran either InetLoad or WCAT, depending on the tests being done. They communicated with the SUT over one or two 100-BaseTX Ethernets. When running WCAT, the WCAT client programs communicated with the WCAT controller over the same 100BaseTX Ethernet(s) used to communicate with the SUT. Using the same network for both controlling WCAT clients and testing the SUT does not interfere with the test measurements because the control communications occur only before a test starts and after it is over. There are no WCAT control communications during a test. The PC client systems were 200MHz Pentium Pro systems. All of the systems used the same operating system: Windows NT Server 4.0 with Service Pack 3. The SUT also had the TCP/IP driver hot fix from June 1997 and Microsoft's Internet Information Server (IIS) version 3.0 installed. Figure 5: ProLiant 2500 Test Lab Configuration

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26

W
HITE
P
APER
(cont.)
19
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Figure 6 shows the test lab configuration used for the ProLiant 7000 testing. The number of client
systems and networks was also determined by experimentation until the CPUs were 100%
utilized. Table 18 shows the actual number of client systems used and the configurations for each
test. There were always two networks used in the ProLiant 7000 tests.
Table18: ProLiant 7000 Test Lab Configuration
Test
# of Client Systems
# of Simulated Users and Worker Threads
per Client System
ILS Connect
8
50
ILS Add
4
20
ILS Direct Lookup
8
50
All PS Tests
3
11
Each of the PC client systems ran either InetLoad or WCAT, depending on the tests being done.
They communicated with the SUT over one or two 100-BaseTX Ethernets. When running
WCAT, the WCAT client programs communicated with the WCAT controller over the same 100-
BaseTX Ethernet(s) used to communicate with the SUT. Using the same network for both
controlling WCAT clients and testing the SUT does not interfere with the test measurements
because the control communications occur only before a test starts and after it is over. There are
no WCAT control communications during a test.
The PC client systems were 200MHz Pentium Pro systems. All of the systems used the same
operating system: Windows NT Server 4.0 with Service Pack 3. The SUT also had the TCP/IP
driver hot fix from June 1997 and Microsoft’s Internet Information Server (IIS) version 3.0
installed.
Figure 5: ProLiant 2500 Test Lab Configuration