Start/notes.ini Parameters/UPDATE_NOTE_MINIMUM

UPDATE_NOTE_MINIMUM

Parameter: UPDATE_NOTE_MINIMUM
Short description: Minimum number of changed notes (documents) the Update task requires before it refreshes a view index. Default 20. Higher values reduce Updater load on heavily used databases.

Profile

Parameter
UPDATE_NOTE_MINIMUM
Syntax
UPDATE_NOTE_MINIMUM=<count>
Default
20 (note changes since last view update)
Values
Integer > 0
Category
Performance / Memory (Updater tuning)
GUI equivalent
none (notes.ini only)
Related
UPDATE_ACCESS_FREQUENCY, UPDATE_IDLE_TIME, UPDATE_DISABLE_VIEWS, Updaters, Update_Suppression_Limit, Update_Suppression_Time
Available since
Domino 6

Description

  • The Update task refreshes view indexes only when two conditions are met:
      1. Since the last update, at least UPDATE_NOTE_MINIMUM notes (documents) have been changed in the database.
      1. The view has been opened within the last 7 days (default; see UPDATE_ACCESS_FREQUENCY).
  • If the conditions aren't met, the Updater skips the view — it will instead be refreshed on next open.
  • Higher values (e.g. 100) reduce Updater load on servers with very many small document changes.
  • Lower values keep view indexes more up-to-date but cost more CPU/disk.

Example

UPDATE_NOTE_MINIMUM=50
  • Updater refreshes a view only when at least 50 notes have been changed since the last update.

Notes

  • Takes effect only after a server restart or restart of the Update task.
  • Works together with UPDATE_ACCESS_FREQUENCY (controlling the 7-day threshold).
  • Increase makes sense on servers receiving many document changes per view (e.g. mail servers, large workflow databases).
  • Decrease makes sense if users complain that views take a long time to open the first time — then the Updater is being too conservative.
  • Affects only view updates by the Update task; Updall ignores this threshold.

Sources (HCL Product Documentation)