# Data FinOps and Cost Optimization > Data FinOps applies the FinOps Foundation's operating model — Inform → Optimize → Operate — to consumption-based data and analytics platforms. The defining difference from infrastructure FinOps: tradi Parent: [Data Analysis](https://llms-explorer.com/tree/data-analysis/) · 15 facets · 89 facts · page: https://llms-explorer.com/tree/data-finops-and-cost-optimization/ ## Overview - Data FinOps applies the FinOps Foundation's operating model - Inform → Optimize → Operate - to consumption-based data and analytics platforms. The defining difference from infrastructure FinOps: traditional cloud bills for provisioned resources over time, while data cloud platforms bill for activity - queries executed, bytes scanned, and consumption of virtual units (Snowflake credits, BigQuery slots, Databricks DBUs). Cost therefore lives in workload telemetry (queries, jobs, pipelines, platform metadata), not in a server inventory. — [source](https://llms-explorer.com/sources/mdb-context-hub/da-37-data-finops-cost-optimization/#overview) - The 2025 FinOps Framework formalized Scopes and a dedicated "FinOps for Data Cloud Platforms" technology category covering Snowflake, Databricks, BigQuery, Redshift, and Microsoft Fabric (finops.org/framework/scope, 2025; 2025 Framework). The discipline pairs data engineers, data scientists, product, and finance to connect spend to value. — [source](https://llms-explorer.com/sources/mdb-context-hub/da-37-data-finops-cost-optimization/#overview) - Scope note: this skill covers analytics/warehouse FinOps. For MongoDB / Atlas cost and sizing, defer to mongodb-cost-optimization. — [source](https://llms-explorer.com/sources/mdb-context-hub/da-37-data-finops-cost-optimization/#overview) ## The three FinOps phases applied to data - Inform - ingest billing exports + query history + metadata; allocate shared/transient compute; report, forecast, and build unit economics. — [source](https://llms-explorer.com/sources/mdb-context-hub/da-37-data-finops-cost-optimization/#the-three-finops-phases-applied-to-data) - Optimize - query tuning, storage lifecycle, workload placement, rate optimization (commitments), right-sizing. — [source](https://llms-explorer.com/sources/mdb-context-hub/da-37-data-finops-cost-optimization/#the-three-finops-phases-applied-to-data) - Operate - make cost-awareness a daily habit: tagging policy, governance, budgets, anomaly alerts, chargeback. (FinOps phases, 2025; State of FinOps 2025) — [source](https://llms-explorer.com/sources/mdb-context-hub/da-37-data-finops-cost-optimization/#the-three-finops-phases-applied-to-data) ## Cloud data warehouse cost models (know the unit before optimizing) - Snowflake - credits / virtual warehouses. Compute bills per-second of active warehouse runtime with a 60-second minimum on every start. Each warehouse size step (XS→S→M→L…) doubles credits/hour. On-demand credits run ~$2–4 each; commitments ~$1.50–2.50. Storage and serverless features (clustering, MVs) bill separately. (Snowflake cost controls, 2025; SELECT pricing, 2025; Revefi 2026 guide) — [source](https://llms-explorer.com/sources/mdb-context-hub/da-37-data-finops-cost-optimization/#cloud-data-warehouse-cost-models-know-the-unit-before-optimizing) - BigQuery - on-demand vs Editions/slots. — [source](https://llms-explorer.com/sources/mdb-context-hub/da-37-data-finops-cost-optimization/#cloud-data-warehouse-cost-models-know-the-unit-before-optimizing) - On-demand: $6.25/TB scanned (first 1 TB/mo free per project). Billed on columns selected, not rows returned - LIMIT does not cut cost; fewer columns + partition/cluster pruning do. — [source](https://llms-explorer.com/sources/mdb-context-hub/da-37-data-finops-cost-optimization/#cloud-data-warehouse-cost-models-know-the-unit-before-optimizing) - Editions (capacity): pay-as-you-go slot-hours - Standard ~$0.04, Enterprise ~$0.06, Enterprise Plus ~$0.10. 1-yr commit ~25–30% lower, 3-yr ~40% lower. — [source](https://llms-explorer.com/sources/mdb-context-hub/da-37-data-finops-cost-optimization/#cloud-data-warehouse-cost-models-know-the-unit-before-optimizing) - Crossover: sustained >~100 slots usually favors capacity over on-demand. Autoscaling bills slots allocated, not used, scales in steps of 100 with a 1-minute floor - a 10s query still costs a full minute. (BigQuery pricing, 2025; Editions intro, 2025; Revefi slot guide, 2025) — [source](https://llms-explorer.com/sources/mdb-context-hub/da-37-data-finops-cost-optimization/#cloud-data-warehouse-cost-models-know-the-unit-before-optimizing) - Databricks - DBUs. Bill = DBU rate × node count × runtime hours × cloud VM list price (the VM is separate, except serverless which bundles it). DBU rate is fixed per SKU; the SKU choice dominates cost: — [source](https://llms-explorer.com/sources/mdb-context-hub/da-37-data-finops-cost-optimization/#cloud-data-warehouse-cost-models-know-the-unit-before-optimizing) - All-Purpose Compute - highest rate (~$0.55/DBU Premium). — [source](https://llms-explorer.com/sources/mdb-context-hub/da-37-data-finops-cost-optimization/#cloud-data-warehouse-cost-models-know-the-unit-before-optimizing) - Jobs Compute - 40–60% cheaper than All-Purpose; migrating scheduled work here is the single highest-return change. — [source](https://llms-explorer.com/sources/mdb-context-hub/da-37-data-finops-cost-optimization/#cloud-data-warehouse-cost-models-know-the-unit-before-optimizing) - SQL Warehouses - SQL Classic (~$0.22/DBU) cheapest, SQL Pro (~$0.55), Serverless SQL (~$0.70–0.91, infra bundled). — [source](https://llms-explorer.com/sources/mdb-context-hub/da-37-data-finops-cost-optimization/#cloud-data-warehouse-cost-models-know-the-unit-before-optimizing) - Photon - vectorized C++ engine; faster but raises the DBU rate - a 3× faster query may cost ~1.5× DBUs/hr, so validate net savings. — [source](https://llms-explorer.com/sources/mdb-context-hub/da-37-data-finops-cost-optimization/#cloud-data-warehouse-cost-models-know-the-unit-before-optimizing) - Standard tier sunset on AWS/GCP Oct 2025, Azure by Oct 2026. (CloudZero, 2026; Flexera guide, 2026; Revefi guide, 2026) — [source](https://llms-explorer.com/sources/mdb-context-hub/da-37-data-finops-cost-optimization/#cloud-data-warehouse-cost-models-know-the-unit-before-optimizing) ## Query cost attribution & chargeback/showback - Showback = show teams their consumption without billing them (central budget absorbs cost). Chargeback = bill teams directly via internal transfer. Showback first builds trust; chargeback drives accountability. (Revefi showback vs chargeback, 2025) — [source](https://llms-explorer.com/sources/mdb-context-hub/da-37-data-finops-cost-optimization/#query-cost-attribution-chargebackshowback) - Snowflake: QUERY_ATTRIBUTION_HISTORY gives per-query compute cost; WAREHOUSE_METERING_HISTORY gives warehouse credit usage; query tags associate queries to teams/projects. (Snowflake attributing cost, 2025) — [source](https://llms-explorer.com/sources/mdb-context-hub/da-37-data-finops-cost-optimization/#query-cost-attribution-chargebackshowback) - Databricks: system.billing.usage (Unity Catalog) + the custom_tags field on each record; tag clusters/jobs via Terraform. (Databricks attribution queries, 2025) — [source](https://llms-explorer.com/sources/mdb-context-hub/da-37-data-finops-cost-optimization/#query-cost-attribution-chargebackshowback) - FOCUS 1.3 (ratified Dec 2025) added shared-cost allocation, commitment datasets, and recency signals - the first spec making cross-provider warehouse FinOps tractable. (DataLakehouseHub FinOps, 2026) — [source](https://llms-explorer.com/sources/mdb-context-hub/da-37-data-finops-cost-optimization/#query-cost-attribution-chargebackshowback) ## Unit economics - Move past raw warehouse cost to value-linked metrics: cost per query, per pipeline, per dashboard, per model run, per TB processed/stored; plus storage decay / dark-data ratio and commitment-utilization score. These connect billing exports to unit consumption (credits/DBUs/slots) so leaders can decide what to scale, tune, or retire. (FinOps value insight, 2025; Revefi KPIs, 2025; Vantage unit economics, 2025) — [source](https://llms-explorer.com/sources/mdb-context-hub/da-37-data-finops-cost-optimization/#unit-economics) ## Methodology (Inform → Optimize → Operate) - Identify the billing unit for each platform (credits / slots / DBUs) and where it accrues. You cannot optimize what you cannot price. — [source](https://llms-explorer.com/sources/mdb-context-hub/da-37-data-finops-cost-optimization/#methodology-inform-optimize-operate) - Inform - establish visibility. Ingest billing exports + query history (QUERY_ATTRIBUTION_HISTORY, system.billing.usage, BQ INFORMATION_SCHEMA.JOBS). Build a cost dashboard and a baseline. — [source](https://llms-explorer.com/sources/mdb-context-hub/da-37-data-finops-cost-optimization/#methodology-inform-optimize-operate) - Allocate & attribute. Enforce tags at the framework level - in dbt profiles, Airflow operators, and query runners - not by asking analysts to remember. Decide showback vs chargeback. — [source](https://llms-explorer.com/sources/mdb-context-hub/da-37-data-finops-cost-optimization/#methodology-inform-optimize-operate) - Define unit economics. Pick 2–3 metrics (cost/query, cost/dashboard, cost/pipeline) that map to business value; track them over time. — [source](https://llms-explorer.com/sources/mdb-context-hub/da-37-data-finops-cost-optimization/#methodology-inform-optimize-operate) - Optimize - usage. Right-size warehouses; tune auto-suspend; add partition/cluster pruning + MVs; convert heavy dbt models to incremental; tier/lifecycle storage; move scheduled Databricks jobs to Jobs Compute. — [source](https://llms-explorer.com/sources/mdb-context-hub/da-37-data-finops-cost-optimization/#methodology-inform-optimize-operate) - Optimize - rate. Move sustained workloads to commitments/Editions; validate Photon net savings; consolidate idle warehouses. — [source](https://llms-explorer.com/sources/mdb-context-hub/da-37-data-finops-cost-optimization/#methodology-inform-optimize-operate) - Operate - sustain. Resource monitors / budgets with hard caps; cost-anomaly alerts to Slack; cost in PR review (state:modified+); periodic heavy-model and dark-data review. — [source](https://llms-explorer.com/sources/mdb-context-hub/da-37-data-finops-cost-optimization/#methodology-inform-optimize-operate) ## Practical Patterns - Right-size by parallelism test. If doubling Snowflake warehouse size halves query time, the workload is parallelizable and the bigger size is cost-neutral but faster. If it doesn't, you're overpaying. (Yuki guide, 2025) — [source](https://llms-explorer.com/sources/mdb-context-hub/da-37-data-finops-cost-optimization/#practical-patterns) - Auto-suspend tiers. ~60s for BI/interactive warehouses, ~30s for programmatic ETL (dbt/Airflow/Tasks). Most workloads tolerate the resume delay. (Anavsan, 2025) — [source](https://llms-explorer.com/sources/mdb-context-hub/da-37-data-finops-cost-optimization/#practical-patterns) - Prune before you scan. Partition on date; cluster large tables on predictable filter columns; use materialized views for repeated aggregations. Partition pruning is the single biggest cost+perf lever in both Snowflake and BigQuery. (e6data, 2025; Flexera tuning, 2026) — [source](https://llms-explorer.com/sources/mdb-context-hub/da-37-data-finops-cost-optimization/#practical-patterns) - Incremental dbt models with predicates. Process only new/changed rows; add incremental_predicates to bound the merge scan window. Bilt Rewards cut ~$20K/mo BigQuery; some models dropped 3h→40m. (dbt reduce BigQuery costs, 2025; TDS incremental, 2025) — [source](https://llms-explorer.com/sources/mdb-context-hub/da-37-data-finops-cost-optimization/#practical-patterns) - dbt + Snowflake cost formula: Total Cost = Warehouse Size × Runtime × Run Frequency. Every optimization reduces one of the three. (dbt 4 decisions, 2025) — [source](https://llms-explorer.com/sources/mdb-context-hub/da-37-data-finops-cost-optimization/#practical-patterns) - Storage lifecycle tiering. Move dormant data to COOL/COLD tiers (Snowflake Storage Lifecycle Policies cut 55–90% for dormant data); use periodic clones instead of long Time Travel windows. (Snowflake storage lifecycle, 2025; analytics.today, 2025) — [source](https://llms-explorer.com/sources/mdb-context-hub/da-37-data-finops-cost-optimization/#practical-patterns) - Anomaly alerts to humans. Snowflake Cost Anomalies (GA Dec 2025) decomposes 28 days into trend + weekly seasonality and flags deviations; route to Slack/email and pair with Resource Monitor hard caps. (Snowflake cost anomalies GA, 2025; Anomaly Insights, 2025) — [source](https://llms-explorer.com/sources/mdb-context-hub/da-37-data-finops-cost-optimization/#practical-patterns) ## Anti-Patterns - Optimizing performance without pricing the unit. A "faster" Photon or larger-warehouse query can cost more. Always check net DBUs/credits, not just wall-clock. — [source](https://llms-explorer.com/sources/mdb-context-hub/da-37-data-finops-cost-optimization/#anti-patterns) - LIMIT to save BigQuery cost. On-demand bills bytes scanned across selected columns - LIMIT changes nothing. Select fewer columns and prune partitions instead. — [source](https://llms-explorer.com/sources/mdb-context-hub/da-37-data-finops-cost-optimization/#anti-patterns) - **SELECT * in models/dashboards.** Forces full-column scans on columnar engines; explodes cost at scale. — [source](https://llms-explorer.com/sources/mdb-context-hub/da-37-data-finops-cost-optimization/#anti-patterns) - Auto-suspend too long (or off). Idle warehouses burn credits; a 10-minute auto-suspend on a bursty BI warehouse wastes most of every hour. — [source](https://llms-explorer.com/sources/mdb-context-hub/da-37-data-finops-cost-optimization/#anti-patterns) - Tag-when-you-remember. Manual per-analyst tagging yields unallocatable spend. Enforce tags in dbt/Airflow/runners. — [source](https://llms-explorer.com/sources/mdb-context-hub/da-37-data-finops-cost-optimization/#anti-patterns) - 90-day Time Travel everywhere. Long CDP retention silently multiplies storage cost; clone instead. — [source](https://llms-explorer.com/sources/mdb-context-hub/da-37-data-finops-cost-optimization/#anti-patterns) - Editions/commitments before measuring. Buying slots/commitments for spiky, low-volume workloads locks in waste - short, spiky queries usually stay cheaper on-demand. — [source](https://llms-explorer.com/sources/mdb-context-hub/da-37-data-finops-cost-optimization/#anti-patterns) - Photon-by-default. It raises the DBU rate; only worth it when the speedup outpaces the rate increase. — [source](https://llms-explorer.com/sources/mdb-context-hub/da-37-data-finops-cost-optimization/#anti-patterns) ## Troubleshooting - "Bill spiked overnight." Check cost-anomaly view; query QUERY_ATTRIBUTION_HISTORY / system.billing.usage / BQ JOBS for the top consumers by tag in the window; look for a runaway scheduled job, a removed LIMIT-less full scan, or auto-suspend regression. — [source](https://llms-explorer.com/sources/mdb-context-hub/da-37-data-finops-cost-optimization/#troubleshooting) - "BigQuery cost high but queries look small." It's bytes scanned, not returned - inspect total_bytes_processed; add partition/cluster filters; cache or materialize repeated aggregations. — [source](https://llms-explorer.com/sources/mdb-context-hub/da-37-data-finops-cost-optimization/#troubleshooting) - "Snowflake warehouse always-on." Verify AUTO_SUSPEND and that no keep-alive query/dashboard polls it; consolidate near-idle warehouses; set a Resource Monitor. — [source](https://llms-explorer.com/sources/mdb-context-hub/da-37-data-finops-cost-optimization/#troubleshooting) - "Can't attribute spend to teams." Tags missing at source - instrument dbt query-comment/tags, Airflow operator tags, Databricks Terraform custom_tags; backfill via query-text parsing only as a stopgap. — [source](https://llms-explorer.com/sources/mdb-context-hub/da-37-data-finops-cost-optimization/#troubleshooting) - "Databricks bill dominated by one SKU." Audit system.billing.usage by SKU; migrate scheduled work off All-Purpose to Jobs Compute (40–60% cheaper). — [source](https://llms-explorer.com/sources/mdb-context-hub/da-37-data-finops-cost-optimization/#troubleshooting) - "Storage cost creeping up." Check Time Travel/Fail-safe retention and dark-data ratio; apply lifecycle tiering; drop or archive stale tables. — [source](https://llms-explorer.com/sources/mdb-context-hub/da-37-data-finops-cost-optimization/#troubleshooting) ## References - FinOps for Data Cloud Platforms - finops.org (2025) - scope, capabilities, billing models. — [source](https://llms-explorer.com/sources/mdb-context-hub/da-37-data-finops-cost-optimization/#references) - 2025 FinOps Framework / Scopes (2025) - framework update. — [source](https://llms-explorer.com/sources/mdb-context-hub/da-37-data-finops-cost-optimization/#references) - State of FinOps 2025 (2025) - practitioner trends. — [source](https://llms-explorer.com/sources/mdb-context-hub/da-37-data-finops-cost-optimization/#references) - Why warehouse cost isn't enough - FinOps value (2025) - unit economics. — [source](https://llms-explorer.com/sources/mdb-context-hub/da-37-data-finops-cost-optimization/#references) - Snowflake - Cost controls for warehouses (2025) - credits, resource monitors. — [source](https://llms-explorer.com/sources/mdb-context-hub/da-37-data-finops-cost-optimization/#references) - Snowflake - Attributing cost (2025) - QUERY_ATTRIBUTION_HISTORY, query tags. — [source](https://llms-explorer.com/sources/mdb-context-hub/da-37-data-finops-cost-optimization/#references) - Snowflake - Cost anomalies GA (Dec 2025) - anomaly detection. — [source](https://llms-explorer.com/sources/mdb-context-hub/da-37-data-finops-cost-optimization/#references) - Snowflake - Storage lifecycle policies (2025) - tiering. — [source](https://llms-explorer.com/sources/mdb-context-hub/da-37-data-finops-cost-optimization/#references) - SELECT - Snowflake pricing explained (2025) & SELECT.dev - tooling. — [source](https://llms-explorer.com/sources/mdb-context-hub/da-37-data-finops-cost-optimization/#references) - BigQuery pricing (2025) & Editions intro (2025). — [source](https://llms-explorer.com/sources/mdb-context-hub/da-37-data-finops-cost-optimization/#references) - Revefi - BigQuery slot cost (2025), Snowflake guide (2026), Databricks guide (2026), showback vs chargeback (2025), KPIs (2025). — [source](https://llms-explorer.com/sources/mdb-context-hub/da-37-data-finops-cost-optimization/#references) - CloudZero - Databricks pricing (2026) & Flexera Databricks guide (2026). — [source](https://llms-explorer.com/sources/mdb-context-hub/da-37-data-finops-cost-optimization/#references) - Databricks - cost attribution via system tables (2025). — [source](https://llms-explorer.com/sources/mdb-context-hub/da-37-data-finops-cost-optimization/#references) - dbt - Cost Insights, 29 ways to optimize costs, Fusion announce, reduce BigQuery costs (2025). — [source](https://llms-explorer.com/sources/mdb-context-hub/da-37-data-finops-cost-optimization/#references) - Bluesky - getbluesky.io - Snowflake workload optimization. — [source](https://llms-explorer.com/sources/mdb-context-hub/da-37-data-finops-cost-optimization/#references) - e6data - Snowflake query optimization (2025) & Flexera Snowflake tuning (2026) - pruning/clustering/MVs. — [source](https://llms-explorer.com/sources/mdb-context-hub/da-37-data-finops-cost-optimization/#references) - Vantage - automate unit economics (2025). — [source](https://llms-explorer.com/sources/mdb-context-hub/da-37-data-finops-cost-optimization/#references) - DataLakehouseHub - FinOps for warehouses with open billing data / FOCUS 1.3 (2026). — [source](https://llms-explorer.com/sources/mdb-context-hub/da-37-data-finops-cost-optimization/#references) ## Related skills - mongodb-cost-optimization - MongoDB/Atlas cost (defer there). — [source](https://llms-explorer.com/sources/mdb-context-hub/da-37-data-finops-cost-optimization/#related-skills) - da-28-realtime-olap-databases - OLAP engine internals / perf. — [source](https://llms-explorer.com/sources/mdb-context-hub/da-37-data-finops-cost-optimization/#related-skills) - da-13-data-engineering-and-pipelines - pipeline engineering. — [source](https://llms-explorer.com/sources/mdb-context-hub/da-37-data-finops-cost-optimization/#related-skills) - da-10-tools-and-languages - SQL/dbt/warehouse tooling. — [source](https://llms-explorer.com/sources/mdb-context-hub/da-37-data-finops-cost-optimization/#related-skills) - da-30-data-governance-catalogs - tagging/metadata governance. — [source](https://llms-explorer.com/sources/mdb-context-hub/da-37-data-finops-cost-optimization/#related-skills) ## Project ideas - Build a cost-attribution dashboard by ingesting Snowflake's QUERY_ATTRIBUTION_HISTORY or Databricks' system.billing.usage table, tagged by team, to move from showback toward defensible chargeback. — [source](https://llms-explorer.com/tree/data-finops-and-cost-optimization/) *(AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.)* - Convert a heavy, full-refresh dbt model to an incremental model with bounded incremental_predicates, and measure the resulting drop in warehouse runtime and cost. — [source](https://llms-explorer.com/tree/data-finops-and-cost-optimization/) *(AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.)* - Set up a cost-anomaly alert, such as Snowflake's native anomaly detection, that routes to Slack, paired with a hard-cap resource monitor as a backstop. — [source](https://llms-explorer.com/tree/data-finops-and-cost-optimization/) *(AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.)* - Design a storage lifecycle policy that tiers dormant data to cool or cold storage tiers and replaces long Time Travel retention windows with periodic clones, to cut storage spend on rarely-queried data. — [source](https://llms-explorer.com/tree/data-finops-and-cost-optimization/) *(AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.)* ## Where this helps - Any team running a consumption-priced data warehouse such as Snowflake, BigQuery, or Databricks that needs to move from an unattributed bill to actively priced, attributable, and optimized spend. — [source](https://llms-explorer.com/tree/data-finops-and-cost-optimization/) *(AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.)* - Deciding whether to move a workload from on-demand pricing to a capacity commitment, based on whether usage is sustained enough — roughly 100+ slots or equivalent — to make the commitment pay off. — [source](https://llms-explorer.com/tree/data-finops-and-cost-optimization/) *(AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.)* - Diagnosing an overnight bill spike by tracing it back to a specific team, job, or query pattern using per-query cost-attribution data rather than guessing from the aggregate bill. — [source](https://llms-explorer.com/tree/data-finops-and-cost-optimization/) *(AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.)* - Deciding whether a faster engine feature like Databricks Photon is actually worth adopting for a given workload, since it can raise the per-unit rate even while cutting wall-clock time. — [source](https://llms-explorer.com/tree/data-finops-and-cost-optimization/) *(AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.)* ## Common mistakes - Adding a LIMIT clause to a BigQuery query expecting it to reduce cost, when on-demand pricing bills by bytes scanned across selected columns, not rows returned. — [source](https://llms-explorer.com/tree/data-finops-and-cost-optimization/) *(AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.)* - Running SELECT * against a columnar warehouse table in a model or dashboard, forcing a full-column scan that needlessly inflates the cost of every query built on it. — [source](https://llms-explorer.com/tree/data-finops-and-cost-optimization/) *(AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.)* - Relying on analysts to manually tag their own queries or jobs for cost attribution, which reliably produces unallocatable spend instead of enforcing tags at the framework level. — [source](https://llms-explorer.com/tree/data-finops-and-cost-optimization/) *(AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.)* - Buying slot or DBU commitments before actually measuring whether the workload is sustained enough to benefit, locking in cost for spiky, low-volume usage that would have stayed cheaper on-demand. — [source](https://llms-explorer.com/tree/data-finops-and-cost-optimization/) *(AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.)* ## Known issues - Photon and similar faster execution engines raise the underlying DBU or credit rate even as they cut wall-clock time, so a 3x speedup does not automatically mean net savings. — [source](https://llms-explorer.com/tree/data-finops-and-cost-optimization/) *(AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.)* - BigQuery's autoscaling slots bill in 100-slot steps with a 1-minute floor, meaning even a 10-second query gets billed for a full minute of allocated capacity. — [source](https://llms-explorer.com/tree/data-finops-and-cost-optimization/) *(AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.)* - Long Time Travel or Fail-safe retention windows silently multiply storage cost over time, and the effect compounds quietly unless someone specifically audits storage-cost trends. — [source](https://llms-explorer.com/tree/data-finops-and-cost-optimization/) *(AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.)* - The FinOps-for-data discipline is still maturing — the FOCUS 1.3 spec that made cross-provider warehouse cost comparison tractable was only ratified in December 2025, so tooling and conventions in this space are comparatively young. — [source](https://llms-explorer.com/tree/data-finops-and-cost-optimization/) *(AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.)* ## Context files - [Data FinOps and Cost Optimization](https://llms-explorer.com/downloads/sources/mdb-context-hub/da-37-data-finops-cost-optimization.md)