Coherence HotCache GoldenGate Batch Processing Takes Twice The Time With Coherence 12.2.1.3.2 Compared To 12.1.2.0.4
(Doc ID 2551849.1)
Last updated on AUGUST 28, 2023
Applies to:
Oracle Coherence - Version 12.2.1.3.0 and laterInformation in this document applies to any platform.
Goal
Does explicit thread pool improves HotCache GoldenGate replicat performance?
Documentation says as follows:
- goldengate.handler.hotcache.mode=tx, -Dcoherence.hotcache.concurrency=1
In tx mode with a concurrency property value of 1, HotCache iterates and applies a transaction worth of trail file operations on a single thread (the GoldenGate Java Adapter thread). The group of operations comprising the transaction is determined by the value of the GoldenGate replicat GROUPTRANOPS property. The default value of the concurrency property is 1. This configuration may exhibit greater throughput than the operation mode configuration, even though it is still single-threaded and therefore poses no data correctness risks.
- goldengate.handler.hotcache.mode=tx, -Dcoherence.hotcache.concurrency>1
In tx mode with a concurrency property value greater than 1, HotCache applies a transaction worth of operations in parallel on multiple HotCache threads. The group of operations comprising the transaction is determined by the value of the GoldenGate replicat GROUPTRANOPS property. This configuration should exhibit greater throughput than single-threaded configurations and throughput generally increases with the number of threads configured to a maximum of eight times the number of cores on the HotCache host.
Solution
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
Goal |
Solution |
Note: |
References |