On 14/12/16 22:05, Real, Elizabeth (392K) wrote:
However, we noticed that while on the ldap client and as a regular user we type “w” to see who is logged on this machine, it takes a while before we get a response with the results. If we type “w” again the response is very fast due to caching.
One way to avoid slow responses is to index whatever you will support searches for, and then set the "unchecked" limit. That's the limit for how many candidate entries a search is willing to examine after consulting indexes, scope etc. If there are more, the search fails immediatly with adminSizeExceeded.
That way you get a quick failure instead of a uselessly large result slowly - provided you take care to index the attributes the user may search for. "Uselessly large" as in - if the user got 100 entries in response to the "w", he'd likely rather type in another character than then browse through the list of results.