Start/notes.ini Parameters/Update_Suppression_Limit

Update_Suppression_Limit

🛠️
Parameter: Update_Suppression_Limit
Short description: Maximum number of update requests within a time window before view updates for a database are suppressed – protects against overload from “hyperactive” apps.

Profile

Parameter
Update_Suppression_Limit
Category
Performance / Memory
Component
Server
Available since
9.0
Supported versions
9.0.1, 10.0, 11.0, 12.0, 14.0, 14.5, 14.5.1
GUI equivalent
notes.ini only (no GUI)
Possible values
Integer (number of update requests)

Description

When an application triggers a large number of writes in a short time, the Update task can end up in a continuous loop and block CPU / I/O. Update_Suppression_Limit defines the threshold: if a database exceeds this number of update requests within the time window defined by Update_Suppression_Time, further updates for that database are temporarily suppressed (logged in the server log). The indexes are then caught up only on the next regular pass.

Example configuration

Update_Suppression_Limit=100
Update_Suppression_Time=15

Notes & pitfalls

  • Values that are too low can affect normal applications – check logs for “Update suppressed” messages.
  • Only effective in combination with Update_Suppression_Time.
  • Takes effect after a server restart.
  • For an affected app, review view logic / indexing strategy instead of raising the threshold permanently.