Calculate how many concurrent jobs a fleet of Jenkins agents can support.
Each agent's theoretical daily capacity is its available hours divided by the average build duration; multiplying by agent count gives the fleet's theoretical maximum. Real fleets never hit 100% utilization — time is lost to provisioning, queueing gaps, retries, and idle periods — so multiplying by a realistic utilization factor (commonly 60–80% for busy CI fleets) converts the theoretical ceiling into an achievable daily throughput estimate.
buildsPerDay = agents × (hoursPerDay / avgBuildTimeHrs) × utilization
70% is a reasonable default for actively used CI fleets; ephemeral cloud agents that spin up on-demand can approach 85–90%, while static agent pools with uneven load across timezones or teams often sit closer to 50–60%.
This calculator estimates achievable throughput from a fixed fleet size; the executor requirement calculator works in the opposite direction, solving for how many executors are needed to hit a target throughput.
It represents build agents each assumed to run one build at a time; if agents run multiple executors concurrently, multiply agent count by executors-per-agent first to get an equivalent single-build-slot count.