HP LH4r HP Netserver & Microsoft Terminal Server 4.0 - Page 16

Test Results

Page 16 highlights

Test Procedures The server and all clients were rebooted prior to each test run. Once the server and clients had successfully booted, the required number of TSE client sessions (i.e., 1-6 client sessions per client workstations) was started on each client. Then, the Performance Monitor was started as a background task on the server. Each Visual Test script was then started manually, as quickly as possible. Once all the clients had completed execution of the script, the Performance Monitor was stopped and all temporary files were deleted from the server. Test Results This section characterizes the behavior (i.e., elapsed time, processor utilization, network utilization and memory utilization) of HP NetServers with various client loads (i.e., 1, 12, 24, 36, 48, 60 and 72). In order to establish an application baseline (0) value, the script was run at the server and the Performance Monitor was used to monitor server activity. The application baseline value is included on some of the charts under the "0" column. Hewlett-Packard Company 16

  • 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
  • 27
  • 28
  • 29
  • 30

Hewlett-Packard Company
16
Test Procedures
The server and all clients were rebooted prior to each test run. Once the
server and clients had successfully booted, the required number of TSE client
sessions (i.e., 1-6 client sessions per client workstations) was started on each
client. Then, the Performance Monitor was started as a background task on
the server. Each Visual Test script was then started manually, as quickly as
possible. Once all the clients had completed execution of the script, the
Performance Monitor was stopped and all temporary files were deleted from
the server.
Test Results
This section characterizes the behavior (i.e., elapsed time, processor
utilization, network utilization and memory utilization) of HP NetServers with
various client loads (i.e., 1, 12, 24, 36, 48, 60 and 72).
In order to establish an application baseline (0) value, the script was run at the
server and the Performance Monitor was used to monitor server activity. The
application baseline value is included on some of the charts under the "0"
column.