Hello, Mohib,
We use OpenDJ, as we are aware of the GLUU planning to discontinue support of the OpenLDAP. OpenLDAP is the backend server, we created, where we can create as many users as we want for test purposes, as it is mentioned already above.
Problem here is the time GLUU takes to synchronize that many users from the OpenLDAP to OpenDJ. I beleive, that this is because there is ldapsearch to all entries, because of only the changed entries (let's say that we want to check and update openDJ for only the changed entries, this could for example be done by looking just the parameter "modifyTimestamp"). This is certainly not the case here, as I can see in this printout:
```
200000 entries - 1 entry updated
____________________________________
2018-12-10 15:06:52,613 INFO [Thread-1359] [gluu.oxtrust.ldap.cache.service.CacheRefreshTimer] (CacheRefreshTimer.java:318) - Attempting to load entries from source server
2018-12-10 15:07:19,427 INFO [Thread-1359] [gluu.oxtrust.ldap.cache.service.CacheRefreshTimer] (CacheRefreshTimer.java:327) - Found '200000' entries in source server
```
For the other question, I am not sure what you mean by:
> you need to 'separate' your Gluu-OpenDJ bit from oxAuth Server.
You mean, problem will be solved with two gluus, each installed on a different VM, in order for each to manage different kind of tasks? Doesn't this just add to complicity on already complicated Cache Refresh part? Do you have a working example on how this works?