free_tool
Latency Budget Calculator
A latency target is only real once it's divided up. Set the p95 you want to promise, then spend it across the hops a request passes through — network, app, database, cache, external calls — and see exactly where the budget goes and which hop to attack first.
Budget remaining
75ms
175ms of 250ms used · 70%
Biggest consumer: App / business logic (60ms).
- Network / TLS
- 20ms8%
- CDN / edge
- 10ms4%
- App / business logic
- 60ms24%
- Database
- 40ms16%
- Cache
- 5ms2%
- External API
- 30ms12%
- Serialization / render
- 10ms4%
Blowing your latency target and not sure which hop to attack? I'll profile the real request path and find the cheapest milliseconds to cut.
Find the slow hop — book a callA budgeting model for the mean path. Tail latency compounds differently — parallel calls overlap, retries stack — but allocating the budget is where every performance plan starts. Share the link to align on targets.
how_it_works
A budget you can defend in review
Pick the number you want to promise — say a 250ms p95 — then give each hop its slice. The total either fits under the line or it doesn't, and the breakdown shows the one hop eating most of the budget. That's almost always where the cheapest win is.
Treat it as a contract: when a feature wants to add a 60ms call, you can see immediately whether the budget has room or what has to get faster to make space. Performance stops being a vibe and becomes a number the team agrees on.