Pipeline Runtime Calculator
Calculate total runtime of a CI/CD pipeline across sequential and parallel stages.
About Pipeline Runtime Calculator
Total CI/CD pipeline runtime is the sum of every stage that must run sequentially, plus the duration of the slowest stage within any parallel group (since parallel stages complete together, bounded by whichever one takes longest): total = sum(sequential_stages) + max(parallel_group_stages). Queue delay waiting for an available executor adds on top of the pipeline's own execution time.
Formula
totalRuntime = sum(sequentialStages) + max(parallelGroupStages) + queueDelay
- S_i
- Duration of sequential stage i in seconds
- P_j
- Duration of parallel stage j in seconds
- Q
- Queue delay in seconds
- T
- Total pipeline runtime in seconds
Worked example
With the default values below, Pipeline Runtime Calculator returns Total Pipeline Runtime of 390. Change any input above and every figure here is recalculated in your browser.
Inputs used
- Sequential Stage Durations
- 60, 90, 45, 30
- Parallel Stage Group Durations
- 120, 90, 150
- Queue Delayaccepts 0–36,000 seconds
- 15 seconds
Results
- Total Pipeline Runtime
- 390 seconds
- Total Pipeline Runtime
- 6.50 minutes
- Sequential Stage Time
- 225 seconds
- Parallel Group Time
- 150 seconds
- Time Saved by Parallelism
- 210 seconds
Step by step
- 1Sum of sequential stages= 225s
- 2Slowest parallel stage (bounds the group)= 150s
- 3Pipeline duration: sequential + parallel group= 375s
- 4Total runtime including queue delay= 390s
Assumptions and limits
- The result is derived only from the 3 inputs listed above. Anything not among them is not part of the calculation.
- In particular, this calculator does not take inflation, tax, fees or charges or compounding frequency into account.
- Figures are rounded for display to 2 decimal places, so totals built from several rounded parts can differ slightly from the unrounded arithmetic.
How these calculators are built and tested is described on the Methodology page. If a figure looks wrong, please report it.
Frequently Asked Questions
Why is the parallel group's time just the maximum, not the sum?
Stages running in parallel execute concurrently on separate executors, so the group as a whole only takes as long as its slowest member — the faster stages simply finish early and wait.
How can I use this to decide what to parallelize?
Moving a slow, independent stage (e.g. a lengthy test suite) into its own parallel group alongside other independent stages reduces total pipeline time by removing it from the sequential sum, at the cost of using another executor concurrently.
Does queue delay vary a lot in practice?
Yes — on shared CI infrastructure during peak hours, queue delay can exceed the pipeline's own execution time; provisioning more executors or using ephemeral cloud runners reduces this variability.
What if I have multiple parallel groups in one pipeline?
Compute each parallel group's max independently, then add all of them plus the sequential stage sum for the full pipeline duration.