Data replication deployments sizing and capacity planning guide

This article provides baseline resource and process sizing guidelines for OCI GoldenGate Data Replication deployments. You and your implementation teams can use this as a structured starting point for selecting deployment capacity and beginning configuration and integration testing.

This article covers:

This article doesn’t cover:

For hybrid topologies, size each component according to its operating model. A customer-managed source-side Extract still requires host and database capacity even when it sends changes to OCI GoldenGate.

Note: This document provides baseline sizing guidance but does not guarantee performance, scalability, or capacity. Actual resource consumption varies with transaction volume, transaction size, transformations, topology, latency requirements, and target performance. Complete a proof of concept using production-representative workloads before deploying to production.

Provide reasonable headroom during initial testing. Undersized deployments can experience resource pressure, trail growth, replication lag, or process instability. Monitor the limiting stage before increasing resources or parallelism.

Basis for these recommendations

The sizing recommendations in this document are not based on a single benchmark or synthetic workload. GoldenGate processes a wide range of transaction profiles, data models, and replication topologies, so no single throughput figure can represent all customer environments.

Instead, the guidance in this document reflects a combination of:

These recommendations provide a practical starting point for infrastructure provisioning and deployment planning. Actual resource requirements depend on workload characteristics including transaction volume, transaction size, redo generation rates, latency requirements, transformation complexity, network conditions, and target-system performance.

Customers should treat these recommendations as baseline guidance and validate them through proof-of-concept testing and operational monitoring before production deployment.

Workload classification tiers

Before selecting a sizing profile, classify the workload using the table below. These labels describe planning complexity; they do not map redo rates or table counts to a guaranteed OCPU requirement. When demand varies, test the busiest sustained period and the recovery workload.

Attribute Small Medium Large X-Large
Target Workload Profile Dev / QA or low volume Department OLTP Enterprise OLTP / DW High volume or complex topology
Avg Redo per Hour (GB) < 1 GB 1-100 GB 100-300 GB > 300 GB
Replication Scope Limited source and target scope Several workload partitions Multiple sources or targets High concurrency or extensive fan-out
Sizing Emphasis Functional validation Sustained demand Peak and recovery capacity Partitioning and failure boundaries

Note: The size of the database, TPS (Transactions Per Second), and table count alone are not reliable predictors of resource consumption. Collect source redo/log bytes, transaction characteristics, captured trail bytes, and wire traffic separately. For Oracle sources, validate redo measurements with the DBA and avoid counting duplicate archived-log copies or RAC threads more than once.

Initial sizing workflow

  1. Measure the source workload.

    • Collect the redo generation rate.
    • Understand transaction characteristics.
    • Identify the source and target count.
  2. Select a workload profile.

    • Use the Workload Classification Tiers table to identify the required test cases.
  3. Create data replication resources.

    • Select base OCPUs and autoscaling. Confirm the cloud, region, build, and storage limit.
  4. Configure GoldenGate.

  5. Establish a monitoring baseline.

    • Capture consumed OCPUs, memory, process lag, and trail growth from day one.
  6. Validate sizing.

    • Run normal, sustained peak, initial-load, and outage-recovery workloads.
  7. Adjust resources as needed.

    • Change the limiting resource or supported process setting, and repeat the test.

Compute and storage sizing

OCI GoldenGate allocates resources to managed deployments. The following table summarizes example base configurations and the documented allocation model. Development and production values are initial planning guidance. The larger values are configuration examples rather than workload tier recommendations.

Sizing philosophy:

Resource Development / Test Production Start Larger Example Maximum Base
Base OCPUs 1 4 8 24
Base Memory Allocation 16 GB 64 GB 128 GB 384 GB
Base Network Allocation 1 Gbps 4 Gbps 8 Gbps 24 Gbps
Storage (Trails, other files) 500 GB 2 TB 4 TB 12 TB

OCPU guidance

Memory guidance

Storage and I/O guidance

Trail retention policy

Base trail retention on business recovery objectives, operational procedures, and the maximum expected outage duration of downstream systems. The required window must also cover restart, catch-up, operator response, and any additional replay requirement.

Example starting retention targets:

Deployment Type Recommended Trail Retention
Development / QA 4-8 hours
Production (single target) 24 hours
Production (critical workloads) 48-72 hours
Cross-region / WAN deployments 72+ hours

These are example starting targets. The selected window must cover the actual recovery procedure and fit within the confirmed deployment storage limit.

Trail storage calculation

When sizing trail storage, account for:

Use this formula:

Required Trail Storage = Peak Trail GB/hour x Retention Hours x Safety Factor

Example: 100 GB/hour x 24 hours x 1.5 = 3,600 GB (3.6 TB)

The safety factor is a planning baseline, not a managed-service allocation rule. Use measured trail-generation bytes for each local trail copy, add the non-trail reserve, and include the complete outage, restart, catch-up, and response interval without counting the same data twice.

Note: The example illustrates the calculation, and it is not a single-deployment capacity recommendation. Validate retention and workload partitioning against the confirmed capacity of each deployment.

GoldenGate process count recommendations

The the following table provides recommended process counts per OCI GoldenGate Data Replication deployment for each workload tier. These counts assume a single-source, multi-target deployment pattern. For multi-source configurations, multiply the Extract count by the number of source databases and adjust the OCPU count accordingly.

GG Process Small Medium Large X-Large
Extract (Integrated) 1 1-2 1-2 2-4
Distribution Paths 1-2 2-4 4-8 8-16
Replicat (Classic) 1-2 2-5 5-15 15-30
Replicat (Parallel) 1 1-2 2-4 4-8
Replicat (Coordinated) 1-2 2-5 5-10 10–0
Max Concurrent Processes 2-4 8-14 16-34 36-70

For multiple sources, account for each supported capture scope and adjust compute accordingly. Apply the console and concurrent-process allowance in OCPU Guidance, then validate memory, target capacity, and peak demand. Partition the workload across deployments when one deployment cannot meet the tested requirement.

Extract process guidelines

Distribution Service guidelines

Replicat process guidelines

OCPU consideration

Disaster recovery topology guidance

OCI GoldenGate operates the service infrastructure. Select a managed recovery topology according to business recovery objectives and feature availability in the chosen cloud and region. Database, network, replication, and application recovery remain part of the complete design.

Single deployment

Primary and peer deployments

Deployment backups and maintenance

Monitoring and metrics baseline

Establish a monitoring baseline from day one. Track service consumption, process performance, database resources, and the complete source-to-target route continuously for production deployments.

OCI Monitoring metrics

You can review the full list of available metrics in Data Replication Metrics.

Configure alarms in OCI Monitoring for process failure, freshness breaches, stalled progress, and forecast storage exhaustion. Thresholds should allow time for operator response. The OCI Notifications service delivers these alarms.

Initial sizing validation criteria

After deployment and representative workload testing, validate sizing against the application objectives. Define numerical lag, resource, and catch-up thresholds for each workload instead of treating them as universal service limits.

A properly sized deployment should exhibit:

Include initial-load overlap, backups, maintenance, and forecast growth in the test. Record achieved rates, worst-case lag, retained storage, recovery time, consistency results, and the conditions requiring a new sizing exercise.

Pre-provisioning checklist

Complete the following checklist before provisioning the initial OCI GoldenGate deployment. Gathering this information in advance reduces deployment delays and post-deployment resizing.

  1. Collect peak and average redo log generation rate from the source DB (per hour, per day).
  2. Identify replicated tables, row sizes, LOBs, largest transactions, filtering, and transformations.
  3. Determine source and target counts, deployment placement, and LAN / WAN / cross-cloud routes.
  4. Confirm supported endpoint combinations and deployment technology.
  5. Confirm the latency SLA (data freshness requirement) with the application owner.
  6. Select base OCPUs and autoscaling; record console and concurrent process allowances.
  7. Size each retained trail copy, recovery backlog, non-trail reserve, and checkpoint-protected purge policy.
  8. Validate measured wire throughput and route latency during normal, peak, and recovery demand.
  9. Measure supplemental logging impact and validate source mining and target apply capacity.
  10. Define source/target privileges, credentials, access policies, DNS, routing, and required listener ports.
  11. Choose a recovery topology and confirm peer, backup, and build availability in the selected cloud.
  12. Plan the initial load and a consistent synchronization boundary. Retain logs/trails through catch-up.
  13. Establish monitoring, alarms, operator ownership, and representative test acceptance criteria.

Disclaimer

Oracle based these recommendations on common deployment patterns and internal testing. Actual resource requirements may vary depending on workload characteristics, including transaction complexity, DML/DDL mix, network latency, target database performance, and supplemental logging configuration.

These recommendations reflect common deployment characteristics across Oracle GoldenGate customer environments and Oracle internal engineering experience. They intend to provide a practical starting point for capacity planning rather than a substitute for workload-specific performance validation.

Oracle Corporation and its affiliates make no warranties, express or implied, regarding the accuracy, completeness, or suitability of these recommendations for a specific environment. Customers are responsible for validating all recommendations and sizing guidance against their own production workloads prior to go-live.