Start/notes.ini Parameters/FTUPDATE_IDLE_TIME

FTUPDATE_IDLE_TIME

Pause (in seconds) between two full-text index operations of the separate FT thread. Only takes effect together with UPDATE_FULLTEXT_THREAD=1. Default 5.

Profile

Parameter
FTUPDATE_IDLE_TIME
Syntax
FTUPDATE_IDLE_TIME=<seconds>
Default
5 (seconds of pause between FT index operations)
Values
Integer in seconds
Prerequisite
UPDATE_FULLTEXT_THREAD=1
Category
Performance / Memory (Updater tuning)
GUI equivalent
None (notes.ini only)
Related
UPDATE_IDLE_TIME, UPDATE_IDLE_TIME_MS, FTUPDATE_IDLE_TIME_MS, UPDATE_FULLTEXT_THREAD, UPDATE_DISABLE_FULLTEXT
Available since
Domino 6

Description

  • When UPDATE_FULLTEXT_THREAD=1 is active, full-text index maintenance runs in its own Updater thread.
  • For this FT thread, FTUPDATE_IDLE_TIME defines the pause between two FT index operations — completely independently of the view thread, which is controlled via UPDATE_IDLE_TIME.
  • Default is 5 seconds, identical to the default of UPDATE_IDLE_TIME.
  • Lower values (e.g. 23) speed up FT index maintenance at the cost of additional CPU/disk load.
  • For finer resolution, FTUPDATE_IDLE_TIME_MS (in milliseconds) is also available.

Example

UPDATE_FULLTEXT_THREAD=1 UPDATE_IDLE_TIME=2 FTUPDATE_IDLE_TIME=5
  • View thread tuned more aggressively (2 s pause), FT thread at default behavior (5 s pause).
  • Useful when FT updates would otherwise put too much load on the machine.

Notes

  • Only takes effect when UPDATE_FULLTEXT_THREAD=1 is set; without a separate FT thread, the value is ignored.
  • Takes effect only after a server restart or restart of the Update task.
  • Before lowering the value, check:
    • CPU and disk utilization,
    • length of the FT update queue (console: show stat update),
    • whether UPDATE_DISABLE_FULLTEXT=1 (FT updates handled entirely via program documents) would be more efficient.
  • Has no effect on the Updall task.

Sources (HCL Product Documentation)