HP ProLiant 4500 Performance Analysis and Capacity Planning for Microsoft Site - Page 12

ProLiant 2500 ILS Bottlenecks, ProLiant 7000 ILS Bottlenecks

Page 12 highlights

WHITE PAPER (cont.) 1...2 • the type of CPU in the system, its speed, the number of processors, and how much of the CPU is utilized • the type of network, its speed, the number of Network Interface Cards (NICs), and the device drivers for the NICs • the amount and type of memory in the system • the operating system • the server software • the disk subsystem ProLiant 2500 ILS Bottlenecks Connect, Add, and Direct Lookup: The performance measurements for the ProLiant 2500 show that it is possible to create loads that can fully utilize the CPU. Analysis of Connect, Add, and Direct Lookup Operations follows: Table 10: Analysis of ProLiant 2500 Operations Resource Bottleneck Comments CPU Primary Fully utilized Network No The total network traffic is less than 3% of the available bandwidth. Memory No The page fault rate indicated by the "Pages/sec" measurement is low. Operating System Not enough Unless ILS implementation details are known, you cannot information determine where the performance bottlenecks are. ILS Software Not enough Unless ILS implementation details are known, you cannot Information determine where the performance bottlenecks are. Disk No Subsystem There is almost no paging and other disk accesses are low. ProLiant 7000 ILS Bottlenecks Connect, Add, and Direct Lookup: The performance measurements for the ProLiant 7000 show that it is possible to create loads that can fully utilize the CPU. Analysis of Connect, Add, and Direct Lookup Operations follows: Table 11: Analysis of ProLiant 7000 Operations Resource Bottleneck Comments CPU Primary Fully utilized Network No The total network traffic is less than 3% of the available bandwidth. Memory No The page fault rate indicated by the "Pages/sec" measurement is low.

  • 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.)
12
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
the type of CPU in the system, its speed, the number of processors, and how much of the CPU
is utilized
the type of network, its speed, the number of Network Interface Cards (NICs), and the device
drivers for the NICs
the amount and type of memory in the system
the operating system
the server software
the disk subsystem
ProLiant 2500 ILS Bottlenecks
Connect, Add, and Direct Lookup:
The performance measurements for the ProLiant 2500 show
that it is possible to create loads that can fully utilize the CPU. Analysis of Connect, Add, and
Direct Lookup Operations follows:
Table 10: Analysis of ProLiant 2500 Operations
Resource
Bottleneck
Comments
CPU
Primary
Fully utilized
Network
No
The total network traffic is less than 3% of the available
bandwidth.
Memory
No
The page fault rate indicated by the “Pages/sec” measurement
is low.
Operating
System
Not enough
information
Unless ILS implementation details are known, you cannot
determine where the performance bottlenecks are.
ILS Software
Not enough
Information
Unless ILS implementation details are known, you cannot
determine where the performance bottlenecks are.
Disk
Subsystem
No
There is almost no paging and other disk accesses are low.
ProLiant 7000 ILS Bottlenecks
Connect, Add, and Direct Lookup:
The performance measurements for the ProLiant 7000 show
that it is possible to create loads that can fully utilize the CPU. Analysis of Connect, Add, and
Direct Lookup Operations follows:
Table 11: Analysis of ProLiant 7000 Operations
Resource
Bottleneck
Comments
CPU
Primary
Fully utilized
Network
No
The total network traffic is less than 3% of the available
bandwidth.
Memory
No
The page fault rate indicated by the “Pages/sec” measurement
is low.