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

ILS User Scenario

Page 8 highlights

WHITE PAPER (cont.) 8... Table 2: ILS Operations Measured ILS Operation Definition and Comments Connect Add Direct Lookup Connection to the ILS directory service. This operation must be done before any application can use ILS and is always done at least once by all ILS applications. The performance of the LDAP command sequence CONNECT, BINDSIMPLE ANONYMOUS, and QUIT was measured to simulate this operation. Note, LDAP requires that CONNECT and a form of BIND are always paired and that a QUIT must be issued before another CONNECT from the same client. ** Add a new online user to the ILS directory. This operation is done after a Connect operation to make the new user accessible to ILS applications. It is done only once by an ILS application, typically just after the connection is made. We measured performance by doing one LDAP CONNECT and one BINDSIMPLE ANONYMOUS, then issuing 100 LDAP ADD commands, and then issuing an LDAP QUIT command. ** Search the ILS directory for a specified user. It must be done after a Connect operation. This is typically the most frequent ILS operation. We measured performance by doing one LDAP CONNECT and one BINDSIMPLE ANONYMOUS, then issuing 100 ILS SEARCH RETURN ALL commands looking for a random user, and then issuing an LDAP QUIT command. ** ** Disk performance is not a significant factor affecting ILS performance, and the amount of memory on a system is not a significant factor affecting PS performance. ILS User Scenario With a goal of determining how many users the SUT can support, a scenario to represent a typical ILS user was developed (see Table 3). Table 3: ILS User Scenario Operation # ILS Command 1 Connect 2 Bind anonymous 3 Retrieve directory 4 Direct Lookup 5 Direct Lookup 6 Direct Lookup 7 Direct Lookup 8 Direct Lookup 9 Direct Lookup Comment Connect to the ILS server Start ILS services Get a listing of all online users Find a specific user Find a specific user Find a specific user Find a specific user Keep this user online Keep this user online Other user scenarios are possible and different scenarios may produce varied platform transaction capacities. For this reason, an Excel spreadsheet computing platform transaction capacities based on different user scenarios has been provided in Appendix A of this paper.

  • 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.)
8
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Table 2: ILS Operations Measured
ILS Operation
Definition and Comments
Connect
Connection to the ILS directory service. This operation must be done before any
application can use ILS and is always done at least once by all ILS applications. The
performance of the LDAP command sequence CONNECT, BINDSIMPLE
ANONYMOUS, and QUIT was measured to simulate this operation. Note, LDAP
requires that CONNECT and a form of BIND are always paired and that a QUIT
must be issued before another CONNECT from the same client.
**
Add
Add a new online user to the ILS directory. This operation is done after a Connect
operation to make the new user accessible to ILS applications. It is done only once
by an ILS application, typically just after the connection is made. We measured
performance by doing one LDAP CONNECT and one BINDSIMPLE
ANONYMOUS, then issuing 100 LDAP ADD commands, and then issuing an
LDAP QUIT command.
**
Direct
Lookup
Search the ILS directory for a specified user. It must be done after a Connect
operation. This is typically the most frequent ILS operation. We measured
performance by doing one LDAP CONNECT and one BINDSIMPLE
ANONYMOUS, then issuing 100 ILS SEARCH RETURN ALL commands looking
for a random user, and then issuing an LDAP QUIT command.
**
**
Disk performance is not a significant factor affecting ILS performance, and the amount of
memory on a system is not a significant factor affecting PS performance.
ILS User Scenario
With a goal of determining how many users the SUT can support, a scenario to represent a typical
ILS user was developed (see Table 3).
Table 3: ILS User Scenario
Operation #
ILS Command
Comment
1
Connect
Connect to the ILS server
2
Bind anonymous
Start ILS services
3
Retrieve directory
Get a listing of all online
users
4
Direct Lookup
Find a specific user
5
Direct Lookup
Find a specific user
6
Direct Lookup
Find a specific user
7
Direct Lookup
Find a specific user
8
Direct Lookup
Keep this user online
9
Direct Lookup
Keep this user online
Other user scenarios are possible and different scenarios may produce varied platform transaction
capacities. For this reason, an Excel spreadsheet computing platform transaction capacities based
on different user scenarios has been provided in Appendix A of this paper.