If an offline integration task runs slowly, use performance diagnosis to check read and write durations, time-consuming operations, and memory garbage collection (GC) time, helping you identify the root cause.
Performance diagnosis entry
-
On the Dataphin home page, navigate to the top menu bar and select Development > Data Integration.
-
At the top menu bar of the Integration page, choose your Project and Environment (selecting an environment is required in the Dev-Prod pattern).
-
In the left-side navigation pane, click on Integration > Batch Pipeline. Then, in the offline integration list, select the desired offline integration task.
-
At the top of the editing area for the selected offline integration task, click Run or Preview.
-
Click View Console at the bottom of the page. In the console, select the
icon to access the performance diagnosis results.NoteIf you remain on the Console > Log Information > Raw Logs page for more than one minute, the system will prompt you to click here to view performance diagnosis. You can then click the indicated icon to proceed to performance diagnosis.
Performance diagnosis introduction
Performance diagnosis covers three areas: Read/Write Diagnosis, Time-consuming Operation Diagnosis, and Memory GC Time Diagnosis. Only abnormal metrics are displayed. Sections with no abnormalities appear empty. Review the findings for each abnormal metric and click Actions in the relevant column to View Suggestions. Follow the recommendations to improve integration task performance.
|
Section |
Description |
|
Read/Write Diagnosis |
Analyzes the ratio of read (wait) and write (wait) times for the data source to identify read/write bottlenecks. A ratio exceeding 60% indicates potential read/write performance issues. |
|
Time-consuming Operation Diagnosis |
Identifies data source operations that take an excessive amount of time. Operations exceeding 180 seconds are flagged as potential performance concerns. |
|
Memory GC Time Diagnosis |
Evaluates the JVM GC time ratio to assess whether the memory configuration is sufficient. A GC time ratio above 30% of the total runtime indicates potential memory configuration issues. |