MessageProcessingBatchSize - System Parameter
Determine the maximum number of Log Events to process in a single iteration.
The MessageProcessingBatchSize System Parameter sets the maximum number of messages Nodinite can process in a single iteration, giving you precise control over performance and resource usage.
The Logging Service is responsible for processing messages and always honors the MessageProcessingBatchSize System Parameter.
Best Practice: We at Nodinite strongly recommend you do NOT set a very large value (e.g., > 10,000). Your Windows Server must have ample RAM for higher values, and you should thoroughly test any changes to this setting.
Management of the MessageProcessingBatchSize System Parameter.
| System Parameter Name | Data Type | Values/Example | Comment |
|---|---|---|---|
| MessageProcessingBatchSize | integer | 100 | Default = 100 (Higher values may induce high memory usage on Nodinite server where Logging Service is running) |
This feature is available from Nodinite version 3.0.
Frequently asked questions
Find more solutions and answers in the Nodinite System Parameters FAQ and the Troubleshooting user guide.
How do I change the value?
Changing a value for the pre-defined System Parameters is described in the generic 'How do I change the System Parameters' article.
What happens if I set a high value?
If you set a high value, the Nodinite Logging Service will attempt to process many messages at once. Depending on the current load and available memory, the operation may or may not succeed. In the worst case, message processing could stop entirely, as messages are processed in order. A single very large message may therefore halt the processing of all Log Events.