What causes the "execute transaction too slow" error in DM logs and how to troubleshoot it

Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.

Original topic: DM日志出现"execute transaction too slow"是什么原因,如何排查

| username: Jjjjayson_zeng

[TiDB Usage Environment] Production Environment
[TiDB Version] v5.4.0
[Reproduction Path] DM experiences CPU and memory explosion after some time
[Encountered Problem: Symptoms and Impact]
Data desynchronization, customer complaints, constantly apologizing to customers
[Resource Configuration] 8c15G
[Attachments: Screenshots/Logs/Monitoring]

| username: weixiaobing | Original post link

See if the downstream execution is too slow.

| username: Jjjjayson_zeng | Original post link

Occasionally slow execution, but TiDB monitoring is normal.

| username: knull | Original post link

Could you please provide the complete information? The log is only partially visible.

| username: okenJiang | Original post link

Could you provide the configuration for each node? How many machines are there with 8c15G? Also, for this kind of question, it’s best to include the DM configuration file, as there are parameters that can be adjusted.

| username: Hacker007 | Original post link

Data synchronization is too slow and can’t keep up with the upstream offset.