Conflate the Server Subscription Queue
Enable conflation at the server level in the server region configuration:
<region ... > <region-attributes enable-subscription-conflation="true" /> </region>
Override the server setting as needed, on a per-client basis, in the client’s
conflate-events settings are:
server, which uses the server settings
true, which conflates everything sent to the client
false, which does not conflate anything sent to this client
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.
Note: This method of conflation is different from the one used for multi-site gateway sender queue conflation. It is the same as the method used for the conflation of peer-to-peer distribution messages within a single cluster.