|
server
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
LDAP query - can I calculate the response time?Hi,
I'm getting complaints that LDAP queries are slow, how can I test this? I was wondered if there was a tool to help me. Gonzo,
Gonzo wrote: > I'm getting complaints that LDAP queries are slow, how can I test this? The easiest way to test LDAP-Queries is downloading ADFind from > I was wondered if there was a tool to help me. joware.net. It fires LDAP queries to the directory services. There's a switch you can use (-stats) that prints out query time and efficiency of the query (in terms of index use). A built-in method you can use is enabling Field Engineering logging at HKLM\SYSTEM\CurrentControlSet\Services\Directory Services\Diagnostics\15 Field Engineering. Key "15 Field Engineering" - set it to 5 for testing. It creates event log entries for LDAP searches then. I think the query time should be included there. Cheers, Florian Thanks,
What would be a typical command then as I thought this would be a GUI tool? Show quoteHide quote "Florian Frommherz" <flor***@frickelsoft.DELETETHIS.net> wrote in message news:OMnfAoi%23JHA.4376@TK2MSFTNGP04.phx.gbl... > Gonzo, > > Gonzo wrote: >> I'm getting complaints that LDAP queries are slow, how can I test this? >> I was wondered if there was a tool to help me. > > The easiest way to test LDAP-Queries is downloading ADFind from > joware.net. It fires LDAP queries to the directory services. There's a > switch you can use (-stats) that prints out query time and efficiency of > the query (in terms of index use). > > A built-in method you can use is enabling Field Engineering logging at > HKLM\SYSTEM\CurrentControlSet\Services\Directory Services\Diagnostics\15 > Field Engineering. Key "15 Field Engineering" - set it to 5 for testing. > It creates event log entries for LDAP searches then. I think the query > time should be included there. > > Cheers, > Florian Gonzo,
Gonzo wrote: > What would be a typical command then as I thought this would be a Call it this way:GUI tool? adfind -default -f "<your filter>" <attributes to return> -stats For example:adfind -default -f "(&(objectClass=user)(objectCategory=person)(physicalDeliveryOfficeName=B*))" dn sAMAccountName physicalDeliveryOfficeName -stats (all in one line). Cheers, Florian Sorry my LDAP is a little rusty, should I need to change any of that example
to replect my domain? Or simply copy and paste and run? Show quoteHide quote "Florian Frommherz" <flor***@frickelsoft.DELETETHIS.net> wrote in message news:uIYQf%23i%23JHA.3544@TK2MSFTNGP04.phx.gbl... > Gonzo, > > Gonzo wrote: > > What would be a typical command then as I thought this would be a GUI > tool? > > Call it this way: > > adfind -default -f "<your filter>" <attributes to return> -stats > > For example: > > adfind -default -f > "(&(objectClass=user)(objectCategory=person)(physicalDeliveryOfficeName=B*))" > dn sAMAccountName physicalDeliveryOfficeName -stats > (all in one line). > > Cheers, > Florian Gonzo,
Gonzo wrote: > Sorry my LDAP is a little rusty, should I need to change any of that You should be able to copy and paste the example. The "default" > example to replect my domain? parameter tells ADfind to use the default domain (the domain the client is currently in). You obviously need to change the LDAP filter to what you need to investigate. The commands and parameters are listed here: http://www.joeware.net/freetools/tools/adfind/usage.htm Cheers, Florian If you want a GUI tool, use LDP.exe and add in the STATS control before you
issue your query. As previoulsy mentioned, ADFIND with the -STATS and the -SELAPSED switches are good. -Brian Show quoteHide quote "Gonzo" wrote: > Thanks, > > What would be a typical command then as I thought this would be a GUI tool? > > > "Florian Frommherz" <flor***@frickelsoft.DELETETHIS.net> wrote in message > news:OMnfAoi%23JHA.4376@TK2MSFTNGP04.phx.gbl... > > Gonzo, > > > > Gonzo wrote: > >> I'm getting complaints that LDAP queries are slow, how can I test this? > >> I was wondered if there was a tool to help me. > > > > The easiest way to test LDAP-Queries is downloading ADFind from > > joware.net. It fires LDAP queries to the directory services. There's a > > switch you can use (-stats) that prints out query time and efficiency of > > the query (in terms of index use). > > > > A built-in method you can use is enabling Field Engineering logging at > > HKLM\SYSTEM\CurrentControlSet\Services\Directory Services\Diagnostics\15 > > Field Engineering. Key "15 Field Engineering" - set it to 5 for testing. > > It creates event log entries for LDAP searches then. I think the query > > time should be included there. > > > > Cheers, > > Florian > > According to 'Network World'
(http://www.networkworld.com/community/node/45949#comment-244254) there
is a free response time monitoring tool you can find at 'Response Time
Monitoring Tool' (http://www.real-user-monitoring.com)
--
ericsully
------------------------------------------------------------------------
ericsully's Profile: http://forums.techarena.in/members/214298.htm
View this thread: http://forums.techarena.in/active-directory/1206129.htmhttp://forums.techarena.in
Howdie!
Am 28.04.2010 17:55, schrieb ericsully: > According to 'Network World' I cannot see the original posting as your response got send to the > (http://www.networkworld.com/community/node/45949#comment-244254) there > is a free response time monitoring tool you can find at 'Response Time > Monitoring Tool' (http://www.real-user-monitoring.com) public newsgroups without a quoting or anything. From the head line of this topic, let me add that there is a STATS-control in LDAP you can call and use. The LDAP server will reply with the search results as well as the statistics on how long it had to search, what the search filter looked like (expanded) and the index it used for searching. You can enable the stats-control in LDAP's options or with the +stats command in ADFind. Cheers, Florian 
Other interesting topics
|
|||||||||||||||||||||||
