Share via

Azure Data Factory Integration Runtime startup time for each activity

Kien Ngo 40 Reputation points
2026-03-31T03:50:39.5466667+00:00

Azure Data Factory Integration Runtime startup time for each activity

Azure Data Factory
Azure Data Factory

An Azure service for ingesting, preparing, and transforming data at scale.

0 comments No comments

1 answer

Sort by: Most helpful
  1. Smaran Thoomu 34,795 Reputation points Microsoft External Staff Moderator
    2026-03-31T07:14:51.3133333+00:00

    @Kien Ngo Hey Kien, it sounds like you’re bumping into the “cold start” delays of the Azure Data Factory Integration Runtime (IR). By default, whenever you kick off a pipeline or activity and there’s no live cluster available, Data Factory spins up a fresh IR compute environment—which can easily take 2–3 minutes (and even longer if you’re using a managed VNet). That delay happens per activity or pipeline run.

    Here are a few ways to shrink that startup time:

    1. Enable TTL (Time-to-Live) • For Data Flow IR: set a TTL of up to 4 hours so the Spark cluster stays alive between runs. • For managed-VNet Copy activities: use the TTL preview feature for pipeline and external activities to avoid repeated cold starts.
    2. Run Data Flows in parallel • In your Data Flow settings, turn on Run in parallel so that multiple sinks share the same warm cluster rather than creating one per sink.
    3. Pre-warm or scale your compute for Custom Activities • If you’re using a .NET custom activity on Azure Batch, keep enough idle nodes in your Batch pool (or configure auto-scale) so tasks don’t wait for nodes to spin up.
    4. Monitor and tune your IR • Use Azure Monitor dashboards and alerts to track IR startup times, cluster utilization, and queue times. • Adjust DIUs or compute size on Copy activities if you see resource constraints.

    Quick check—can you tell me:

    • Which type of IR you’re using (Azure IR vs. self-hosted vs. managed VNet)?
    • What activity types you’re running (Copy, Data Flow, Custom, etc.)?
    • Whether you’ve already configured TTL or parallelism?
    • The typical startup/queue time you’re seeing today?

    With those details we can tailor the recommendations further.

    Reference Docs:

    1. Azure Data Factory Integration Runtime Concepts https://learn.microsoft.com/azure/data-factory/concepts-integration-runtime
    2. Monitor Data Factory with Azure Monitor https://learn.microsoft.com/azure/data-factory/monitor-data-factory
    3. Optimize Performance with Data Flows https://learn.microsoft.com/azure/data-factory/concepts-data-flow-performance

    Note: This content was drafted with the help of an AI system. Please verify the information before relying on it for decision-making.

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.