I'm not an admin, but this looks very useful http://www-01.ibm.com/support/knowledgecenter/SSKTMJ_9.0.1/admin/admn_indexertasksupdateandupdall_r.dita.
One part I notice is:
When a view or folder change is recorded in the queue, Update waits
approximately 15 minutes before updating all view indexes in the
database so that the update can include any other database changes
made during the 15-minute period. After updating view indexes in a
database, it then updates all databases that have full-text search
indexes set for immediate or hourly updates.
It's worth noting the Indexer task updates view indexes as well as the full text indexes. You can split them onto separate threads using UPDATE_FULLTEXT_THREAD=1
in notes.ini. With the more recent versions of Domino you can move the full text indexes onto a separate drive. I'm not sure if that improves update performance.
Please don't use LotusScript to update the full text index in an XPages context. I can't stress that strongly enough. Also, if you want to update the full text index, I'd recommend using the parameter false
instead of true
. The database should always have a full text index in place when it's set up, but you can easily check that.
In recent projects I've been using Jesse Gallagher's frostillicus framework. I notice that the BasicDocumentController class updates the full text index on save of each document, with this code:
if (database.isFTIndexed()) {
database.updateFTIndex(false);
}