USER AND SERVER CONFIGURATION

Tuning Domain Indexer performance
Each time the Domain Indexer task runs, it looks in the Domain Catalog for new databases that have the "Include in multi database indexing" property enabled. It then looks for documents and files in existing databases and file systems that are new or changed since the last time it ran, and adds them to the Domain Index.

To meet the specific needs of your organization, adjust the frequency with which the Domain Indexer runs. Greater frequency results in more up-to-date indexes, but consumes greater CPU resources. By default, the Domain Indexer task runs every 60 minutes. Experiment with different indexing frequencies to yield the best results for your organization.

You can also enhance search performance by tuning the number of indexing threads used by Domain Search. Each indexing thread indexes one repository at a time. With a greater number of threads, the indexing server can index more databases simultaneously, but this requires more CPU utilization, and response to search queries may be slow. With fewer indexing threads, response to queries is faster because of greater CPU availability, but changes are not reflected in the index as quickly.

By default, the indexing server uses two indexing threads per CPU, so a server with two CPUs uses four indexing threads when indexing. By adding the variable FT_Domain_Idxthds=n to the NOTES.INI file of the indexing server, you can control the total number of threads used for indexing on that server. For example, by adding "FT_Domain_Idxthds=8" to the NOTES.INI file of an indexing server with two CPUs, you change the number of indexing threads to eight.

Note Do not exceed eight threads per server or you may degrade the performance of the server, even on servers with more than four CPUs.

Related topics