batchwatch › Google › gemini-2.5-flash
Measured, not promised. Google publishes a completion window of 24 hours and nothing more precise; below is what 238 real batch jobs actually did.
Share of jobs finished, against elapsed time. 238 completions, 30-day window.
The curve is drawn from the pooled measurements, while the headline percentiles above are the median of each contributor's own figures - so the two need not line up exactly. That is deliberate: no single source can move a headline number by sending more data.
Upper end of the measured interval
Plan for 6 min. That is the upper end of a 90% confidence interval around the p90, computed from the measurements themselves. It is deliberately not the median: being wrong toward synchronous costs twice the money, being wrong toward batch can miss a deadline, and those two mistakes are not equally expensive.
The slowest job we actually observed took 14 min. That is one job, not a bound.
Score 0.47 · basis: exact_model
Based on a single contributor, a figure pooled across contributors (not yet a per-contributor median), nothing measured for 6 days.
Pooled across every measurement we have. As more contributors each build their own track record, this figure sharpens into a per-contributor median.
Each measurement is one completed batch job. The duration is end minus start, both timestamped by our server - a client can never submit a duration, and a job we stopped waiting for is recorded as abandoned, never as a fast completion.
| Newest measurement | 2026-08-21T02:39:28.000Z |
|---|---|
| Oldest in window | 2026-08-14T11:51:37.000Z |
| Figures computed | 2026-08-27T09:40:58.000Z |
| Public delay | 15 minutes |
| Percentile method | pooled (1 voting source) |
Timestamps are absolute and in UTC on purpose: this page may be cached, and a relative age would quietly go stale in the cache while an absolute one stays true.
Same numbers, same delay, no key required.
curl "https://batchwatch.dev/v1/curve?provider=google&model=gemini-2.5-flash"
Contributing five measurements in seven days cuts the delay to five minutes and unlocks the decision endpoints (/v1/should-i-batch, /v1/estimate-batchtime). Start on the front page.