goldengate performance https://docs.oracle.com/goldengate/1212/gg-winux/GWUAD/wu_performance.htm#GWUAD684
and
Goldengate 12c Implementors Guide Chapter 9 et. al.
and my list
- LOBs are special case – separate the processing of them with parallel processing groups – and don’t use BATCHSQL tuning parameter on them, obviously make sure there is a PK.
- Baseline with default single extract, data pump, and replicate processes – and make one change at a time – comparing a new benchmark to your baseline.
- DBFS – to be enhanced
- Divide large tables into separate parallel process groups.
- Use Integrated or coordinated mode when possible to take advantage of automatic parallel replicate.
- If you must run in “classic” mode, run parallel process groups for replicate.
- Adding large number of extract processes does not scale linearly.
- Use @RANGE to split very large tables to multiplex data pump and replicate processes groups.
- Expedite your replicate processes by: Configuring your replicate process to alter commit_wait=’NOWAIT’ as the session level:
sqlexec “alter session set commit_wait=’NOWAIT'”;
Don’t do this at the system level if other updates are taking place outside of Goldengate on the target instance as corruption can occur that make transactions un-recoverable.
- Use Goldengate 12c or higher to take advantage of integrated replicate – add more detail
- Goldengate 12c supports up to 5,000 extract and replicate processes per instance – use the following to show how well the cachemgr is doing at automatically managing things – you can manually control this – beyond scope of this doc:
send extract EXT1, cachemgr cachestats
- Use trace to find wait events with GGSCI:
GGSCI> send REP1 trace1 ./dirrpt/REP1.trc
GGSCI> send REP1 trace1 off
GGCSI> exit
view dirrpt/REP1.trc
- Goldengate views used by AWR – accessible by sys / system or anyone with select_catalog_role role granted
DBA_HIST_CAPTURE: Displays the historical statistics information about each capture process for Oracle Streams, Oracle GoldenGate, and XStream capture operations.
DBA_HIST_APPLY_SUMMARY: Displays the historical statistics information about each apply process for Oracle Streams, Oracle GoldenGate, and Oracle XStream.
DBA_HIST_REPLICATION_TBL_STATS: Displays replication table statistics for Oracle GoldenGate and XStream sessions. The information collected in this view is used to display information related to the performance of Streams, GoldenGate, and XStream in the following sections of the AWR report: Replication statistics (GoldenGate and XStream) Streams statistics
- Network tuning – kernel minimums – 12c OUI prerequisite checks this. 8MB is not unusual.
net.core.rmem_max = 4194304
net.core.wmem_max = 4194304
- Increasing TXQUEUELEN to 5000 and beyond for Gb NICS – over > 5,000 if 50ms round on pings from source to target – again baseline before making any changes and make them one at a time and re-benchmark
ifconfig eth1 txqueuelen 5000