Domain Indexer will use multiple threads in order to run quicker. But when the domidx update cycle starts, it will assign a queue to each of the configured threads. The list of databases flagged to be included in the domain index is then spread over these queues. The Domain index thread will continue with the list of database flagged in its queue. In case if current thread is busy with The database will not indexed by other free threads
Thread A is assigned with DB1.nsf, DB2.NSF, DB3.nsf , Index folder "IDX0"
Thread B is assigned with DB4.nsf, DB5.NSF, DB6.nsf, Index folder "IDX1"
So If Thread A is running on DB1.bnsf and taking time and If ThreadB is free, it will not run on DB2.nsf and DB3.nsf as it is assigned to ThreadA.
This is affecting the efficiency of the domain indexer.
Can we update the Domain Indexer thread queue management so that the waiting database will be indexed by the other free thread instead of busy flagged thread.
This will increase the efficiency of the Domain index and it will helpful in completing the process faster.