The problem
A platform team pays for compute in two ways: on-demand capacity that follows traffic, and one or three-year commitments such as Savings Plans that are cheaper but paid whether used or not. FinOps teams typically commit to the steady baseline and leave the peaks on demand, reaching high commitment coverage without paying for idle capacity, but the right level depends on how the traffic moves.
I replayed provisioning and commitment policies on a long run of hourly real traffic, against provisioning for last year’s peak, and measured the cost and the hours left short.
- Team
- Head of platform, SRE, FinOps and the CFO’s office
- Scale
- Tens of millions of requests an hour; a fleet across regions
- Systems
- AWS, Azure or Google Cloud autoscaling, Kubernetes, Datadog or Grafana, Savings Plans or committed-use discounts
- Measure
- Utilisation of provisioned capacity; hours short of capacity; cost against on-demand
What I built
A capacity model that replays real hourly demand under each provisioning policy and reports capacity-hours bought, hours short and unserved traffic. It sets the scaling headroom from the shortfall the business accepts, adds a day-ahead forecast as a floor where it helps, and sizes commitments from the trailing year in quarterly layers instead of once.
Results
I used 42,352 hours of real traffic: user page views on English Wikipedia from 2022 to October 2026, 420 billion in all. Policies were set from 2022 to 2024 and measured on January 2025 to October 2026.
Headroom and the forecast
The shortfall rises quickly below about 15% headroom. At a target of no more than 0.5% of hours short, reactive scaling needs 14% headroom. Adding a day-ahead forecast as a floor (3.3% hourly error, against 3.7% for the same hour last week) helps only at the tightest targets: at 0.2% of hours short it saves 2% of capacity-hours. Traffic this large changes smoothly hour to hour, so the last hour is already a strong guide; the forecast earns its place for scale-up lead time and scheduled events.
Commitments when traffic drifts
Traffic in 2026 ran 15% below 2024. With a 40% commitment discount, a commitment sized once on 2024 traffic left 10% of committed capacity idle; layering commitments quarterly on the trailing year cut that to 9% and came within 0.3% of the best single level chosen in hindsight.
| Commitment | Cost against all on demand | Committed capacity left idle |
|---|---|---|
| Sized once on 2024 traffic | 68.5% | 10.3% |
| Layered quarterly on the trailing year | 67.8% | 8.8% |
| Hindsight best single level | 67.5% |
Data and method
- Data
- Wikimedia Foundation pageviews API: hourly user page views for English Wikipedia, all access methods, 2022-01-01 to 2026-11-01, 42,352 hours. Page views stand in for requests to a platform’s front end.
- Policies
- Fixed at the 2022 to 2024 99.9th percentile hour plus 20%; capacity each hour set to the previous hour times a headroom factor; the same with a day-ahead 99th percentile forecast as a floor
- Forecast
- Gradient-boosted quantile and point regression on hour, weekday, day of year and lags of a day or more
- Commitments
- 40% discount on committed capacity; reactive capacity at 20% headroom as the need; one-year layers bought each quarter
- Measures
- Utilisation; share of hours short; unserved share of traffic; cost against all on demand
Limitations
- Page views are not compute. A real platform maps requests to instances through its own load tests; the replay uses that mapping.
- Hourly data hides minute-level bursts; scale-up time and minimum fleet size are set from the platform’s own metrics.
- The real 40% rate depends on the provider, term and payment option.
- Wikipedia’s traffic is one site’s pattern. The method carries over and the levels are re-measured on the client’s traffic.
How I would take it live
- Export a year of request and instance metrics from Datadog, Grafana or the cloud provider
- Fit the request-to-capacity mapping from load tests, then replay current and proposed scaling policies
- Set headroom from the agreed shortfall target and move commitments to quarterly layers
- Review utilisation, shortfall hours and commitment idle share monthly with FinOps