Data Transmission Service (DTS) offers seven instance classes for data synchronization instances, each with a defined maximum rows per second (RPS) throughput. Choose an instance class based on the volume of incremental data your source instance generates per second.
Instance class specifications are for reference only and are not part of the DTS service level agreement (SLA). DTS can synchronize data within seconds, but latency may increase due to source instance workload, network bandwidth, network latency, or destination instance write performance. DTS does not guarantee second-level latency for all synchronization tasks.
Instance classes
| Instance class | Maximum RPS |
|---|---|
| micro | Fewer than 200 |
| small | 2,000 |
| medium | 5,000 |
| large | 11,000 |
| xlarge | 17,000 |
| 2xlarge | 34,000 |
| 4xlarge | 68,000 |
The maximum RPS values in the table are achievable only when all three conditions are met:
The source instance generates rows at or above the maximum RPS of the synchronization instance.
The destination instance write performance is high enough to sustain the maximum RPS.
The network latency between the DTS server and the source or destination instance is less than 2 milliseconds.
Actual RPS varies based on network conditions and the performance of the source and destination instances. The maximum RPS values are for reference only and are not covered by the DTS SLA.
We recommend that you do not use the micro instance class in production environments.
Key concepts
Instance class The performance tier of a data synchronization instance. The number of data records that can be synchronized varies based on the instance class.
Rows per second (RPS) The number of data rows incrementally synchronized to the destination table per second. For example, an instance synchronizing 5,000 rows per second has an RPS of 5,000.
Choose an instance class
Match the instance class to the peak incremental write volume of your source instance:
Estimate your peak RPS. Check the write throughput of your source instance during peak hours — specifically, the number of rows written per second.
Select a class at or above your peak RPS. Choose an instance class whose maximum RPS meets or exceeds your estimated peak to leave headroom.
Verify destination write performance. The destination instance must handle writes at the same rate. If the destination is a bottleneck, actual synchronization throughput will be limited regardless of the instance class.
Check network conditions. If the network latency between DTS and your source or destination exceeds 2 milliseconds, the instance may not reach its rated maximum RPS.
For workloads with highly variable write volumes, choose a class that matches your peak rather than your average.