Job Completion Time Calculator
Estimate total completion time for a Kubernetes Job given parallelism and completions.
About Job Completion Time Calculator
A Kubernetes Job with N completions and parallelism P runs in ceil(N/P) sequential batches, since only P pods run at once. Total wall-clock time is that batch count multiplied by the average time for one pod to finish. Increasing parallelism reduces total time proportionally until you hit cluster capacity limits, at which point new pods queue as Pending instead of running concurrently.
Formula
totalTime = ceil(completions / parallelism) × avgPodDuration
- N
- Total completions required (.spec.completions)
- P
- Parallelism (.spec.parallelism)
- t_p
- Average pod duration in seconds
- T
- Estimated total job wall-clock time in seconds
Worked example
With the default values below, Job Completion Time Calculator returns Estimated Job Completion Time of 5.0. Change any input above and every figure here is recalculated in your browser.
Inputs used
- Total Completionsaccepts 1–10,000,000 tasks
- 100 tasks
- Parallelismaccepts 1–100,000 pods
- 10 pods
- Average Pod Durationaccepts 0.1–86,400 seconds
- 30 seconds
Results
- Estimated Job Completion Time
- 5.0 minutes
- Estimated Job Completion Time
- 0.08 hours
- Sequential Batches
- 10
- Total Time
- 300 seconds
Step by step
- 1Batches = ceil(completions ÷ parallelism)= 10
- 2Total time = batches × avg pod duration= 300s
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
What if pod duration varies a lot between tasks?
Use a higher percentile (p90) rather than the mean for avgPodDurationSeconds, since the slowest pod in each batch determines when the next batch can start — variance directly extends total wall-clock time.
Does raising parallelism always reduce completion time?
Only up to the point where the cluster has spare capacity to actually run that many pods concurrently — beyond that, extra parallelism just means more pods sit Pending waiting for resources.
How is this different from a CronJob?
A Job runs once until it reaches its target completions; a CronJob creates a new Job on a repeating schedule. Use the CronJob schedule calculator to plan recurring runs.