Hello @Chatti, Niharika [E]
One possible reason could be the use of the Script activity, which can be slower than other activities.
To improve the performance of your pipeline, you can try the following:
- Use the Copy activity instead of the Script activity wherever possible. The Copy activity is optimized for data movement and can be faster than the Script activity.
- If you must use the Script activity, try to optimize your script code to make it more efficient. For example, you can try to reduce the number of loops or use more efficient data structures.
- Consider using a more powerful Integration Runtime (IR) if you are not using Auto resolved Integration Runtime. A more powerful IR can handle larger workloads and may improve the performance of your pipeline.
- Check if there are any throttling errors on the sink or if your data store is under high utilization. If so, either reduce your workloads on the data store, or try contacting your data store administrator to increase the throttling limit or available resource.
- Gradually tune the parallel copies. Note that too many parallel copies may even hurt the performance.
If none of these solutions work, you may need to investigate further to identify the root cause of the delay. You can check the pipeline run details to see if there are any errors or warnings that could be causing the delay. You can also monitor the performance of your data store to see if there are any issues that could be impacting the pipeline performance.
I hope this helps.