Start/notes.ini Parameters/UPDATE_FULLTEXT_THREAD

UPDATE_FULLTEXT_THREAD

Parameter: UPDATE_FULLTEXT_THREAD
Short description: Makes the Update task run view updates and full-text index updates in separate threads, so that long FT indexing operations don't block the view update queue.

Profile

Parameter
UPDATE_FULLTEXT_THREAD
Syntax
UPDATE_FULLTEXT_THREAD=1
Values
0 (default, shared thread) / 1 (separate FT thread)
Effect
Update task forks into two threads (Views + FT)
Category
Performance / Memory (Updater tuning)
GUI equivalent
none (notes.ini only)
Related
UPDATE_IDLE_TIME, FTUPDATE_IDLE_TIME, UPDATE_IDLE_TIME_MS, FTUPDATE_IDLE_TIME_MS, UPDATE_DISABLE_VIEWS, UPDATE_DISABLE_FULLTEXT, Updaters
Available since
Domino 8.5

Description

  • By default, a single Updater thread maintains both view indexes and full-text indexes. A long FT indexing operation on a large database can then queue up all subsequent view update requests.
  • UPDATE_FULLTEXT_THREAD=1 splits the Updater into two threads:
    • Thread A: refreshes view indexes
    • Thread B: refreshes full-text indexes
  • Result: view updates keep running while a large FT index is being built.
  • Complementarily, UPDATE_IDLE_TIME (views) and FTUPDATE_IDLE_TIME (FT) can configure the pause between update operations separately for each thread.

Example

UPDATE_FULLTEXT_THREAD=1
UPDATE_IDLE_TIME=3
FTUPDATE_IDLE_TIME=5
  • Separate FT thread enabled.
  • View updates with a 3-second pause between operations, FT updates with a 5-second pause.

Notes

  • Takes effect only after a server restart or restart of the Update task.
  • Particularly useful on servers hosting individual very large databases with FT indexes.
  • Increases CPU demand of the Updater — only worthwhile if the server has enough headroom.
  • Has no effect when UPDATE_DISABLE_FULLTEXT=1 is set (no FT updates by the Updater at all in that case).
  • Can be combined with Updaters=N to run multiple Updater instances in parallel.

Sources (HCL Product Documentation)