- 1 minutes to read
MessageProcessingTimerInterval - System Parameter
The MessageProcessingTimerInterval System Parameter once set how often the Logging Service looked for new messages to process. It has no effect in Nodinite v7; the key remains because upgraded installations still show it.
At a Glance
| Property | Value |
|---|---|
| Key | MessageProcessingTimerInterval |
| Data type | integer (milliseconds) |
| Default | 15000 (ignored) |
| Read by | Nothing; the Logging Service uses fixed intervals |
| Takes effect | Never |
| Status | ⚠️ No effect |
What to Use Instead
Nothing; there is no message processing interval to tune. The Logging Service checks the active Log Database for new messages every 30 seconds and the archive Log Databases every 5 minutes. These intervals are hard-coded, and a change to MessageProcessingTimerInterval is ignored.
Each check processes the whole backlog, batch by batch. To control how much message data the Logging Service holds in memory per batch, use MessageProcessingBatchSize; to skip very large messages, use MessageProcessingMaxBodySize.