AWS DMS performance degradation until stopped and resumed

Hi!

I recommend starting with reviewing the task latency, specifically where the latency is. This will help you narrow down what you should be looking at.

If you see source latency on an AWS DMS task, it can be caused by one or more of the following:

• The source database has limited resources.
• The AWS DMS replication instance has limited resources.
• The network speed between the source database and the AWS DMS replication instance is slow.
• AWS DMS reads new changes from the transaction logs of the source database during ongoing replication.
• AWS DMS task settings are inadequate or large objects (LOBs) are being migrated.

High CDCLatencyTarget is most likely the result of the delay in capturing the change events from the source. If the CDCLatencySource isn't high, but the CDCLatencyTarget is high, the latency could be caused by the following:

• There are no primary keys or indexes in the target
• There are resource bottlenecks in the target
• There are resource bottlenecks in the replication instance
• There is a network issue between the replication instance and the target

Guidance on troubleshooting can be found at How do I troubleshoot high source latency on an AWS DMS task? and How can I troubleshoot high target latency on an AWS DMS task?

If you're able to identify where the latency starts (source/target), reviewing the Performance Insights dashboard for the instance might also help you find any bottlenecks or review counter metrics that may help explain what could be contributing to the slowdown.