Start/notes.ini Parameters/FTUPDATE_IDLE_TIME_MS

FTUPDATE_IDLE_TIME_MS

Millisecond variant of FTUPDATE_IDLE_TIME. Allows finer control of the FT thread's pause when the separate FT thread is active.

Profile

Parameter
FTUPDATE_IDLE_TIME_MS
Syntax
FTUPDATE_IDLE_TIME_MS=<milliseconds>
Values
Integer in milliseconds (e.g. 200, 500, 1000)
Prerequisite
UPDATE_FULLTEXT_THREAD=1
Category
Performance / Memory (Updater tuning)
GUI equivalent
None (notes.ini only)
Related
FTUPDATE_IDLE_TIME, UPDATE_IDLE_TIME, UPDATE_IDLE_TIME_MS, UPDATE_FULLTEXT_THREAD, UPDATE_DISABLE_FULLTEXT
Available since
Domino 7

Description

  • FTUPDATE_IDLE_TIME works in whole seconds — on large, fast servers this resolution is often not sufficient.
  • FTUPDATE_IDLE_TIME_MS sets the same pause in milliseconds instead.
  • If both parameters are set, FTUPDATE_IDLE_TIME_MS takes precedence over FTUPDATE_IDLE_TIME.
  • Only takes effect when UPDATE_FULLTEXT_THREAD=1 is set (separate FT thread). Without a separate FT thread, the value is ignored.
  • Counterpart for view updates: UPDATE_IDLE_TIME_MS.

Example

UPDATE_FULLTEXT_THREAD=1
UPDATE_IDLE_TIME_MS=500
FTUPDATE_IDLE_TIME_MS=1000
  • View thread with 500 ms pause, FT thread with 1000 ms pause between index operations.
  • Result: fast view maintenance, more resource-efficient FT maintenance.

Notes

  • Takes effect only after a server restart or restart of the Update task.
  • Values below 100 ms drastically increase CPU and disk load.
  • Recommendation: first test with FTUPDATE_IDLE_TIME=2, then fine-tune with FTUPDATE_IDLE_TIME_MS if needed.
  • Has no effect on the Updall task.

Sources (HCL Product Documentation)