blob: 8855f4420c2a82a9e5dbb078af22e2320c4fe64d [file] [log] [blame]
---
title: Enabling Queue Conflation to Improve Update Performance
---
<!--
Licensed to the Apache Software Foundation (ASF) under one or more
contributor license agreements. See the NOTICE file distributed with
this work for additional information regarding copyright ownership.
The ASF licenses this file to You under the Apache License, Version 2.0
(the "License"); you may not use this file except in compliance with
the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
-->
Conflation of entry update messages can reduce the number of update messages a client receives, thereby increasing performance. The client receives only the most recent update for a particular entry key.
Conflation is enabled for a cache server region, so all clients receiving updates for a particular region benefit from the conflation. To enable conflation, set the cache servers `enable-subscription-conflation` region attribute to `true`. This region attribute is `false` by default.
The queue management code conflates entry updates as part of the enqueue operation. If the previous enqueued item for that key is also an `update` operation, the queue management code removes that previously enqueued update, leaving only the latest update to be sent when event distribution occurs. For high availability, conflation also occurs for 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 the server documentation at [Conflate the Server Subscription Queue](<%=vars.serverman%>/developing/events/conflate_server_subscription_queue.html).
## <a id="concept_AEFA04AF9ABD42C0A37ED31806596D24__section_BE506A32A8E44073B197B03AC5232C01" class="no-quick-link"></a>Overriding Queue Conflation Per-Client
Override conflation on a per-client basis by setting the conflate-events property in the clients `geode.properties` 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.