AWS Cross-Region Replication

Benchmark statistics are based on product replication engine version 6.0 test results.
Product versions 9.0 and above deliver substantially better performance.

AWS Cross-Region Replication Scenario

Geo-replication scenario:

Moderate ~300,000 inserts per minute into 4 tables in a database hosted on an AWS Virginia based RDS R3.Xlarge instance, geo-replicated asynchronously to an AWS Oregon based smaller RDS R3.Large server.

Database size: ~400GB

Database size increment: ~150MB/min (~200GB/day)

[Geo-replication lag: < 1min]

RDS AlwaysOn type: M4.XLarge (other replications running concurrently)

Virginia RDS R3.XLarge (Primary; ~300,000 inserts per minute into 4 tables)

Resource Utilization Statistics

Virginia RDS R3.XLarge on AWS

Oregon RDS R3.Large (Read-Replica; ~300,000 inserts per minute geo-mirrored with <1min lag)

Resource Utilization Statistics

Oregon RDS R3.Large

Database Size: ~400GB

VA to OR Database size: ~400 GB

RDS AlwaysOn/Geo-Replicate Dashboard: ~300,000 pending changes at any given moment
Geo-Replication lag: <1min

VA to OR Analyze Report 300k inserts lag 1min

RDS AlwaysOn/Geo-Replicate Continuous Synchronization Logs, divided into ~1 min time slots: Number of changes per time slot: ~300,000
Geo-Replication lag: <1min

VA to OR lag 283600 inserts, lag = less than 1 min

RDS AlwaysOn/Geo-Replicate Seeding (initial replication) Statistics
AWS Virginia to AWS Oregon: 23GB/h

RDS Replication Statistics: Continuous Synchronization Logs, divided into ~1 min time slots

Note: for large databases, after the seeding phase, the replication process will require substantial amount of time to catch up with synchronizing the pending changes accumulated during the seeding phase. then will transition to continuous replication with a low lag (may vary based on database structure, parallel replication execution on same RDS AlwaysOn server etc.)

<< Back to Benchmarks