Coherence Persistence Snapshot Creation With Backup Count Is 1 Or More Causes Performance Impact On Cluster
(Doc ID 2456900.1)
Last updated on APRIL 28, 2020
Applies to:Oracle Coherence - Version 188.8.131.52.2 to 184.108.40.206.0 [Release 12c]
Information in this document applies to any platform.
Customers are seeing performance impact on the cluster after enabling backup count in the persistence enabled clusters. Coherence persistence enabled to elastic data storage, on SSD (VM). Customers have seen GC impact and more CPU usage while snapshot creation.
In the Coherence 12c versions currently when issuing an on-demand snapshot, coherence runtime do not close all persistence BDB environments until all the partitions have been snapshotted for the member. This means that there is a potential for memory used be each partition snapshot to be held until the end of the snapshots. Would it be possible to reduce the memory overhead after each snapshot as they are only created for creating on-demand snapshots?
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document