Timeout Budget Planner

Allocate a user-facing deadline across downstream calls, connection and processing time, retries, and safety margin.

Workload values stay in this browser

REQUEST PATH

Set the deadline and work

Describe one user-facing operation and the downstream calls on its critical path. Connection and processing values are budgets for one attempt.

Total user-facing timeout ms Downstream calls Call pattern Concurrent mode models the longest equal-budget call on the critical path. It does not assume unlimited connection or server capacity. Connection budget per attempt ms Processing budget per attempt ms Retries after the initial attempt Safety margin %

BUDGET SUMMARY

Results

Ready to plan

Use the defaults or enter the request path you need to evaluate.

Available timeout per attempt 0 ms Even allocation after retries and safety reserve

Safety-adjusted budget consumed0% 0%

Total timeout0 ms

Safety reserve0 ms

Usable path budget0 ms

Required critical path0 ms

Budget per dependency0 ms

Requested attempt budget0 ms

Maximum retries that fit0

Retry time per dependency0 ms

Modeled critical path

Enter values to see the critical-path equation.

READ THE BUDGET

A deadline must cover the whole critical path.

A dependency timeout is only one slice of the user-facing deadline. Queueing, connections, processing, retries, serialization, and application work all compete for the same elapsed time.

1
Reserve safety time
The safety margin stays outside the dependency budget so the application can finish its own work and return a response.
2
Build the critical path
Sequential dependency budgets add together. Independent concurrent calls are modeled by the longest call.
3
Fund complete attempts
Each retry needs enough remaining time for both its connection and processing budget. A partial attempt is not useful.
4
Stop at the deadline
Pass the remaining deadline downstream and avoid starting work that cannot finish before it expires.

SUGGESTED CHANGES

Ways to improve this plan

Calculate a plan to see suggestions.

Planning model: This calculator uses equal per-dependency budgets and assumes concurrent calls are independent. It does not measure your network or service. Validate the plan with production latency distributions, connection-pool limits, provider quotas, cancellation behavior, and end-to-end tests. Read Choosing Reasonable API Timeouts, then use the concurrency simulation and retry planner for related decisions.