From: Bing D. <Bi...@ci...> - 2000-10-16 22:29:32
|
We are using 5.0v2p2 directory server from MessagingDirect. Given 500 studentIDs, Net::LDAP is used in a cgi script to retrieve name, e-mail address, major, etc. for each ID. Like this: connect ldap foreach (@studentids) { $t0 = new Benchmark; $mesg = $ld->search(base => $BASEDN, scope => 'sub', filter => $filter, attr s => @$attributes, typesonly => 0); $t1 = new Benchmark; $td = timediff($t1,$t0); } disconnect ldap Benchmark shows most 'search' operations contribute 0 seconds. About 20 or so contribute 1 seconds each. So the total execution time is 20 or even more seconds. A note from vendor says the current DS version is 6.1v0 and it can yield 50% speed improvement. Just want to know how much of this performance issue is server related? Any suggestions on how to run ldap search fast on the client side? Thanks, Bing Bing Du <bi...@ta..., 979-845-9577> Texas A&M University, CIS, Operating Systems, Unix |
From: Kurt D. Z. <Kurt@OpenLDAP.org> - 2000-10-16 23:31:16
|
At 05:28 PM 10/16/00 -0500, Bing Du wrote: >Benchmark shows most 'search' operations contribute 0 seconds. About >20 or so contribute 1 seconds each. So the total execution time is 20 >or even more seconds. A note from vendor says the current DS version is >6.1v0 and it can yield 50% speed improvement. Just want to know how >much of this performance issue is server related? Any suggestions on >how to run ldap search fast on the client side? Reduce the number of protocol operations. For example, you might be able to use one search operation instead of 500 hundred. If multiple operations are needed, only serialize operations were needed. For example, you could submit 500 search requests (using the async interface) then await results. |