Quote Originally Posted by jwilleke View Post
Thanks for the feedback.

All of my customer sites, since moving off NetWare (i.e. File and Print directories), are all LDAP access and have one ROOT partition.
Rarely ever had replication issues and almost never used ndsrepair.

Also, in this case, the replication in PILOT was 2-5 minutes with 4 servers each with 11 partitions
  • Admittedly smaller (5 million entries)
  • Admittedly fewer daily connections
  • Had to use ndsrepair regularly (more than once a week)

and when pilot was collapsed to one partition replication is measured in seconds.

Anyone else have thoughts on this subject?

The number of objects is only one interesting factor. The churn on those objects is much more interesting. You could have a billion objects, but if only three of them ever change, that's a much different picture from 100K objects where 20K of them change every second.

Also, what replication strategy are (were) you using? You can tune the method and number of threads.

With lots of replication, you also really need to have a look at the disk subsystem underneath the DIB and see how it is performing. If you're stacking up lots of writes waiting for disk, performance is going to inhale strongly.

ndsrepair more than once a week? That's either crazy or a symptom of a deeper problem.