tencent cloud

Data Transfer Service

Release Notes and Announcements
Release Notes
Announcements
Product Introduction
Overview
Data Migration
Data Sync
Data Subscription (Kafka Edition)
Strengths
Supported Regions
Specification Description
Purchase Guide
Billing Overview
Configuration Change Description
Payment Overdue
Refund
Getting Started
Data Migration Guide
Data Sync Guide
Data Subscription Guide (Kafka Edition)
Preparations
Business Evaluation
Network Preparation
Adding DTS IP Addresses to the Allowlist of the Corresponding Databases
DTS Service Permission Preparation
Database and Permission Preparation
Configuring Binlog in Self-Built MySQL
Data Migration
Databases Supported by Data Migration
Cross-Account TencentDB Instance Migration
Migration to MySQL Series
Migrating to PostgreSQL
Migrating to MongoDB
Migrating to SQL Server
Migrating to Tencent Cloud Distributed Cache
Task Management
Data Sync
Databases Supported by Data Sync
Cross-Account TencentDB Instance Sync
Sync to MySQL series
Synchronize to PostgreSQL
Synchronization to MongoDB
Synchronize to Kafka
Task Management
Data Subscription (Kafka Edition)
Databases Supported by Data Subscription
MySQL series Data Subscription
Data Subscription for TDSQL PostgreSQL
MongoDB Data Subscription
Task Management
Consumption Management
Fix for Verification Failure
Check Item Overview
Cutover Description
Monitoring and Alarms
Supported Monitoring Indicators
Supported Events
Configuring Metric Alarms and Event Alarms via the Console
Configuring Indicator Monitoring and Event Alarm by APIs
Ops Management
Configuring Maintenance Time
Task Status Change Description
Practical Tutorial
Synchronizing Local Database to the Cloud
Creating Two-Way Sync Data Structure
Creating Many-to-One Sync Data Structure
Creating Multi-Site Active-Active IDC Architecture
Selecting Data Sync Conflict Resolution Policy
Using CLB as Proxy for Cross-Account Database Migration
Migrating Self-Built Databases to Tencent Cloud Databases via CCN
Best Practices for DTS Performance Tuning
FAQs
Data Migration
Data Sync
FAQs for Data Subscription Kafka Edition
Regular Expressions for Subscription
Error Handling
Common Errors
Failed Connectivity Test
Failed or Alarmed Check Item
Inability to Select Subnet During CCN Access
Slow or Stuck Migration
Data Sync Delay
High Data Subscription Delay
Data Consumption Exception
API Documentation
History
Introduction
API Category
Making API Requests
(NewDTS) Data Migration APIs
Data Sync APIs
Data Consistency Check APIs
(NewDTS) Data Subscription APIs
Data Types
Error Codes
DTS API 2018-03-30
Service Agreement
Service Level Agreements

Data Migration Specification

PDF
Mode fokus
Ukuran font
Terakhir diperbarui: 2025-05-13 15:39:52

Parameter Description

When purchasing a DTS task, users need to select the specification of the task. Different specifications correspond to different transfer performances. Transfer performance is represented by RPS.
RPS represents the number of rows per second that DTS incrementally migrates from the source database to the target database. For example, if 2000 rows of data are incrementally migrated from the source database to the target database per second, then the RPS is 2000.

Specification

The following specifications are available for the data migration link.
Note:
The RPS (Requests Per Second) may be influenced by several factors including the configuration of the source database, network latency, and the complexity of the data in the source database. The following RPS performance reference for DTS (Data Transfer Service) is based on a benchmark of 1KB per data record. Utilizing larger data records in actual scenarios may result in a decrease in RPS.
Specification
Performance Limit (RPS)
small
2000
medium
5000
large
6000
xlarge
7000
2xlarge
11000

Test Model

Test procedure: Create an incremental migration task between two TencentDB MySQL instances, conduct stress testing on the source database MySQL, and monitor the performance of incremental data migration.
Instance
MySQL Instance Configuration
Reference Limit Performance
Source Database
Instance Specifications: 16-core 32000 MB
Memory: 200 GB
Maximum QPS: 12000
Maximum IOPS: 32000
Target Database
Instance Specifications: 16-core 32000 MB
Memory: 200 GB
Maximum QPS: 12000 Maximum IOPS: 32000
Test Model:
Number of test tables is 20. Each table has about 2 million records. Each record is about 1 KB.
All test tables have a primary key.
Each Transaction generally contains two DML operations, one is COMMIT, with the ratio of INSERT, UPDATE, DELETE being 1:1:1.
Note:
The test results in this section are based on a benchmark of 1KB per data record. In practical applications, larger data records may result in a decrease in Requests Per Second (RPS).

Test Results

After stress testing the small, medium, and large specifications, the results show that the RPS provided by DTS can be achieved under all specifications. Even in scenarios with the maximum network latency, the RPS performance can reach the upper limit in cross-region (China to global) migration results.
Migration Region Type
Maximum Network Latency
Minimum Network Latency
Specification
RPS
Intra-region (China): Guangzhou > Guangzhou
3.46ms
2.14ms
small
2000
2.51ms
2.21ms
medium
5000
10.1ms
2.20ms
large
6000
Cross-region (China): Guangzhou > Beijing
37.6ms
33ms
small
2000
68.2ms
33.2ms
medium
5000
48.2ms
36.4ms
large
6000
Intra-region (Global): Singapore > Singapore
2.31ms
240μs
small
2000
2.45ms
273μs
medium
5000
2.11ms
241μs
large
6000
Cross-region (global): Singapore > Silicon Valley
200ms
174ms
small
2000
201ms
175ms
medium
5000
204ms
175ms
large
6000
Cross-region (China to global): Guangzhou > Silicon Valley
255ms
162ms
small
2000
309ms
151ms
medium
5000
174ms
152ms
large
6000

Bantuan dan Dukungan

Apakah halaman ini membantu?

masukan