All Products
Search
Document Center

Data Transmission Service:Monitor task performance

Last Updated:Mar 28, 2026

DTS performance monitoring lets you view real-time throughput metrics and data-flow topologies for synchronization and migration tasks. Use the Performance Monitoring page to identify bottlenecks, compare source and destination throughput, and determine whether latency originates on the source or destination side.

Prerequisites

Before you begin, ensure that you have:

View performance metrics

  1. Log on to the DTS console.

  2. In the upper-left corner, select the region where your DTS instance resides.

  3. In the left-side navigation pane, click Data Synchronization or Data Migration based on your task type.

    The following steps use a data synchronization task as an example.
  4. On the Data Synchronization page, find your instance and click its ID to open the instance details page.

  5. In the left-side navigation pane, click Performance Monitoring.

  6. Select a tab based on the synchronization phase you want to inspect:

    • Performance of Full Data Synchronization — for the initial bulk data transfer phase

    • Performance of Incremental Data Synchronization — for ongoing change capture and replication

Full data synchronization metrics

On the Performance of Full Data Synchronization tab, start with the Topology of Full Data Synchronization to locate any throughput imbalance between the source and destination, then select a time range in the Performance of Full Data Synchronization section to investigate when performance changed.

Topology of full data synchronization

The topology shows live read/write performance for both the source and destination connections.

DTS and source database

MetricDescription
BPSData read from the source per second (MB/s).
RPSRecords read from the source per second.
Network LatencyNetwork latency between DTS and the source database.

DTS and destination database

MetricDescription
BPSData written to the destination per second (MB/s).
RPSRecords written to the destination per second.
Network LatencyNetwork latency between DTS and the destination database.

Performance of full data synchronization

Select a time range to view trend charts for bandwidth, RPS, read/write response time, and network latency across the full synchronization phase.

Tip: To see the description of a specific metric, hover over the 图标 icon in the upper-right corner of that metric's trend chart.

Incremental data synchronization metrics

On the Performance of Incremental Data Synchronization tab, start with the Topology of Incremental Data Synchronization to identify where throughput drops in the pipeline, then use the trend charts in the Performance of Incremental Data Synchronization section to analyze the affected time range.

Topology of incremental data synchronization

The incremental topology shows data transmission across the modules in the DTS pipeline:

Source database → Data collection module → Data cache module → Data writing module → Destination database

For each connection between modules, the following metrics are displayed:

MetricDescription
BPSData transmitted between modules per second (MB/s).
RPSRecords transmitted between modules per second.
Network LatencyLatency between adjacent modules in the pipeline.

Performance of incremental data synchronization

Select a time range to view trend charts covering three areas:

  • Incremental data collection performance — bandwidth and RPS at the collection layer

  • Log cache module performance — log cache module throughput

  • Incremental data synchronization performance — end-to-end bandwidth, RPS, and synchronization latency

FAQ

  • Where did the Quick Diagnostics feature go? The Quick Diagnostics section moved from the Performance Monitoring page to the Task Management page. To run a quick diagnostic, go to Task Management, click the name of the module you want to check, and then click Quick Diagnostics on the Health Details tab at the bottom of the page.

  • How do I limit throughput for a running task? See Enable throttling for data migration.

What's next