Explanation
Why the waste happens and who it affects.
However, if query volumes drop - due to seasonal cycles, architectural shifts (e.g., workload migration), or inaccurate forecasting - those baseline or committed slots may sit underused. This inefficiency is easy to miss, as the cost remains fixed and detached from usage volume. Autoscaling absorbs bursts, but baselines, commitments, and max slot settings still require active monitoring and manual adjustment. In some organizations, reservations are spread across separate administration projects, exacerbating waste through fragmentation because idle slots are shared only among reservations in the same admin project, region, and edition.
Billing model
The pricing dimensions that drive this cost.
BigQuery offers two primary billing models:
- On-Demand: Billed per TiB of data scanned.
- Capacity-Based (Editions) Reservations: Billed for baseline slots whether or not they are used, plus autoscaled slots for the number of slots scaled rather than slots used. Capacity pricing is ideal for consistent, high-volume workloads. However, when workload patterns are unpredictable or seasonal, reserved slots may remain idle, generating cost without performance benefit. Autoscaled slots are billed per second with a one-minute minimum by default, while optional 1-year or 3-year commitments run for their full term. Unused slots are not refunded, and idle slots are shared by default only among reservations in the same administration project, region, and edition.
How to detect
5 checks to find it in your estate.
- Review reservation utilization trends over a representative period
- Compare committed slots vs. actual slots used per project or workload
- Identify whether query concurrency or runtime metrics justify reservation size
- Assess whether workloads could be served equally well with on-demand pricing or a lower baseline with autoscaling
- Review historical query demand to identify periods of persistent underutilization
How to fix
5 ways to remove the waste.
- Reduce baseline slots, and avoid renewing oversized commitments, if sustained usage is consistently lower than committed capacity
- Consolidate slot reservations across projects to improve pool utilization
- Switch low-concurrency or unpredictable workloads back to on-demand pricing or to a lower baseline with autoscaling
- Implement governance to review reservation adjustments regularly
- Leverage the Reservation Assignment API to dynamically reassign slot pools based on usage
Documentation
Vendor references for pricing and configuration.