Adjust the number of messages read from table queues
- Last UpdatedApr 24, 2025
- 1 minute read
Note: For information on overriding default configuration settings, see Modify configuration settings.
As changes occur for a table, messages are queued for later processing by all configured plugins. The MaxConcurrentMessagesRead key determines the maximum number of messages pulled off the queue per processing loop. AVEVA has determined that five messages is the optimal number for balancing performance and memory usage. You should only change this setting if advised to do so by customer support.
To adjust the number of messages read from table queues
-
In the %DNADataRoot%\RealTime\config\Settings directory, either create or open the RealTime_DataExport.json file.
-
In the following line, change the value to a number greater than 0.
"MaxConcurrentMessagesRead": 5
-
Save the file.
-
Restart the RealTime service.
If the key-value pair does not exist in the file, or if the entered value is 0, then the system:
-
Uses an internal value of 5.
-
Prints a message to the DataExportEngine.log file.
-