Computational Waste Percentage
Definition
Quantifies technical debt and operational inefficiency in data cloud platforms by isolating spend that provided zero business utility. This includes credits/units consumed by failed jobs, resources idling before auto-suspension, or “technical spillage” due to over-provisioning. A higher percentage reveals systemic architectural inefficiency or poor guardrails, whereas a lower percentage indicates a highly tuned environment where spend is strictly aligned with successful processing.
Formula, as published
((Unit Consumed by Failed Jobs + Idle Time + Technical Spillage) / Total Compute Units Consumed) x 100
- Data sources:
- Resource event logs (Active vs. Idle state) System performance metrics (Spillage/Memory telemetry) Usage and activity reports
Calculate it
Example values to start with; replace them with yours.
From the FinOps Foundation
More Anomaly Management KPIs
Definition and formula: Computational Waste Percentage, FinOps KPI library, FinOps Foundation, licensed CC BY 4.0, read 16 Oct 2026. Changed: HTML removed, dashes and British spellings changed, formula split from its data sources and examples. The calculator and the notes are Finitizer’s.
Measured once, a KPI is a number. Tracked daily, it is a practice.
Finitizer computes the KPIs your billing data supports every day, by team and product, across AWS and Google Cloud.
See how Finitizer works