AdLds / Adam stuck every 50s

Question

I have a weird behaviour on my instances of AdLds / Adam.

Every 50 seconds or so, the queries takes longer to execute (2.36 seconds instead of 0.1s) I wrote a simple test program to query my local instance with the same simple query and I get the following screenshot.

I have the same results regardless of the computer I query from or to.

Any idea of the why ?

My query code :

private const string Cx = "LDAP://server:389/CN=Por,DC=XXX,DC=int";
DirectoryEntry de = new DirectoryEntry(Cx) { Username = "username", Password = "password" };

DirectorySearcher ds = new DirectorySearcher(de)
{
      Filter = "(cn=randomUsername)",
      SearchScope = SearchScope.OneLevel
};
SearchResult sr = ds.FindOne();

enter image description here

EDIT Same problem if I use UserPrincipal. It would seem to be configuration related...

EDIT

I've enabled all diagnostics to full verbose on the ADAM instance but no error pops up. No message from garbage collection occurring at the time of the 2s call.

I've added the following to the registry but no changes either :

GC Force Rediscovery Window (sec)
GC Force Wait Expired (sec)
GC Honor Failure Window (sec)

EDIT

I've seen the hotfix ADAM service runs slowly or stops responding during garbage collection but it only applies to W2003 and not W2008R2 / W7

how big is it? how old? is the disk fragmented? have you used the MS compact utility on it? — Dave Bennett, Jan 20 '15 at 16:52
It's brand new installs with very little data. No ms compact. — Vincent, Jan 20 '15 at 17:59
yeah - no need to compact or defrag. have you tried the same with localhost so you can factor our some network thing that happens every 50 seconds? — Dave Bennett, Jan 20 '15 at 18:04
I've tried A queries B, C queries B, A queries D and even on local instances. Same results. — Vincent, Jan 20 '15 at 18:26
@Vincent That's very likely the garbage collector kicking in. "Disk fragmentation" has nothing to do with it. — Tomalak, Jan 21 '15 at 06:55
Is there a way to configure it ? it's a real drawback in performance when I used it from my web application. — Vincent, Jan 21 '15 at 07:23

score 0 · Accepted Answer · edited May 23 '17 at 11:50

0

I found the other on another post : AD LDS slow on first access - Why?

You must specify the full name of the server hosting the AdLds instance. I don't know why at all, it's weird but it works.

edited May 23 '17 at 11:50

Community

1
1

answered Jan 21 '15 at 09:37

Vincent

510
1
5
23

AdLds / Adam stuck every 50s

1 Answers1