Pivotal GemFire® v8.0

Enabling Queue Conflation to Improve Update Performance

Enabling Queue Conflation to Improve Update Performance

You can configure client queues on the cache server to conflate queued messages, so the native client receives only the latest update for a particular entry key.

You enable conflation in the cache server region, so all clients interested in updates in a particular region either get the updates conflated or not. To enable conflation, set the cache server’s enable-bridge-conflation region attribute to true. Conflation is set to false by default.

Queue conflation is performed when an entry update is added to the queue. If the last operation queued for that key is also an update operation, the previously enqueued update is removed, leaving only the latest update to be sent to the client when event distribution occurs. For high availability, the conflation process is also performed on any secondary queues.

Only entry update messages in a cache server region with distributed-no-ack scope are conflated. Region operations and entry operations other than updates are not conflated.

For more information, see Conflate the Server Subscription Queue in the Pivotal GemFire User’s Guide.

Overriding Queue Conflation Per-Client

You can override conflation on a per-client basis by setting the conflate-events property in the native client’s file.

Valid settings are:
  • server. Uses the server settings.
  • true. Conflates everything sent to the client.
  • false.Does not conflate anything sent to the client.