|Configuring Client/Server Event Messaging / Tuning Client/Server Event Messaging|
Conflating the server subscription queue can save space in the server and time in message processing.
<region ... > <region-attributes enable-subscription-conflation="true" /> </region>
conflate-events=falseValid conflate-events settings are:
Conflation can both improve performance and reduce the amount of memory required on the server for queuing. The client receives only the latest available update in the queue for a particular entry key. Conflation is disabled by default.
Conflation is particularly useful when a single entry is updated often and the intermediate updates don’t require processing by the client. With conflation, if an entry is updated and there is already an update in the queue for its key, the existing update is removed and the new update is placed at the end of the queue. Conflation is only done on messages that are not in the process of being sent to the client.