LDAP-UX Integration Performance and Tuning Guidelines

Appendix B DirectoryMark

Search Performance

The following table is an unofficial estimate of Netscape Directory Server v6.02 search performance on selected HP

platforms. If your platform is not listed, it can roughly be interpolated based on the speed of the processor.

Example: Suppose you have a 550mhz A-Class with 2 CPUs. The formula would be to use the results from the

A-Class 440 MHZ. In this case, the estimate would be: 1249 * 550/440 = 1561

The client used to generate these results was an A500 2-Way @ 440mhz running HP-UX 11.00 with the November

1999 patch bundle.

Note: Several TCP performance enhancements we made available in the November 1999

patch bundle. Installing the November 1999 patch bundle or later is highly

recommended.

The HP performance lab has selected several systems for DirectoryMark testing. It should be noted that these are

not official results:

Server DirectoryMark

search performance

N4000 1-Way @ mhz 843

L2000 1-Way @ 440 mhz 835

L2000 2-Way @ 440 mhz 1294

A500 1-Way @ 440 mhz 840

A500 2-Way @ 440 mhz 1249

K260 2-Way @ 160 mhz 452

K460 4-Way @ 160 mhz 625

R380 1-Way @ 180 mhz 226

Note: The above performance numbers were obtained on HP-UX 11.00. Some early test

results indicate that 11i can achieve higher throughput (possibly as much as 30%

higher.) This document will be updated when additional testing data is made available.

The DirectoryMark tool was configured as follows:

• Number of entries: 100

• Operations per thread: 2000

• Search Percentage: 100%

• Directory was already populated (no modify operations)

• ACL type: 3.x/4.0

• Bind: Once as root

• Number of clients: 25

• Seconds to run: 60

• Mode: quiet

• LDAP SDK: libldapssl30.sl

The LDAP server was configured with access logging ON.

Page 17