The Domain Index resides on the Domino server that has been designated as the Domain Search server. It is an index of all the data in databases and file systems on servers in the domain that the administrator has chosen to include in Domain Search. When you build the initial Domain Index, it will be important to free up as many resources on the Domain Search server as possible. The initial build of the index is extremely resource intensive. Memory and CPU are taxed heavily during this process. By eliminating extra server tasks, you can increase the available resources for building the index.
In particular, the Domino server Update task uses the same engine as the Domain Indexer task. If they are both in the Servertasks= line, they will be competing for the same resources.
Code
So, if your server's notes.ini Servertasks= line looks something like this,
Servertasks=AdminP,Amgr,Router,
Replica,Collect,Event,DIIOP,DECS, NNTP,HTTP,Stats,Update,CallConn,Sched
you might want to change it to something like this while building the initial index:
Servertasks=Adminp,Amgr,Replica
After the index is built, you may add the other server tasks back in. But first ask yourself: Will this server ever route mail, need to update calendars (calconn and sched tasks), etc.? If the answer is yes, add the task back in. If the answer is no, eliminate the task completely.
Only add the Update task back in if you plan to full-text-index any databases on the Domain Search server. If there are no databases requiring full-text indexing on the Domain Search server, we recommend eliminating the Update task, since it competes with the Domain Indexer task for resources by using the same engine.
Consider also removing any tasks in the ServerTasksAt lines that will not be needed.
- Cheryl Elmo & Debbie Lynd
