Help Center/ DataArts Studio/ User Guide/ DataArts Migration (Real-Time Jobs)/ Job Performance Optimization/ Overview
Updated on 2025-08-05 GMT+08:00
View PDF

Overview

If the latency of a real-time migration job keeps increasing, the back pressure is high, or the synchronization is too much slower than the expected synchronization speed of the real-time migration job, the possible causes are as follows:

  • Too slow writing at the destination
  • Too slow extraction at the source
  • Other problems (contact technical support)

If data is written to the destination too slowly, data extraction at the source will also be slow. To find out the cause of a slow link, check the write speed at the destination, and then check the upstream.

Slow Writing at the Destination

  1. Check whether the load at the destination has reached the upper limit by checking the monitoring metrics of the data source, such as the CPU usage, memory usage, and I/O.
  1. If the load at the destination has not reached the upper limit, increase the number of concurrent jobs to improve the writing speed.
  2. If the performance is not improved after step 2 is performed, check the performance of the source based on Slow Extraction at the Source.
  3. If you have excluded the source problems, optimize parameters by following the instructions in the link performance optimization document.
  4. If none of the preceding steps work, contact technical support.

Slow Extraction at the Source

  1. Check whether the load at the source has reached the upper limit by checking the monitoring metrics of the data source, such as the CPU usage, memory usage, and I/O.
  2. If the source load has not reached the upper limit, and if the source is a full and incremental MySQL, Oracle, SQL Server, PostgreSQL, or GaussDB migration job in the full extraction phase, or is a Kafka or Hudi migration job with slow extraction, increase the number of concurrent jobs to improve the concurrent extraction rate.

    Data in relational databases such as MySQL, Oracle, SQL Server, PostgreSQL, and GaussDB is extracted in single concurrency mode during incremental migration. Increasing the concurrency does not improve the extraction performance.

  3. If the performance is not improved after step 2 is performed, optimize parameters by following the instructions in the link performance optimization document.
  4. If none of the preceding steps work, contact technical support.