Explanation
Why the waste happens and who it affects.
This leads to significant and often hidden compute consumption for maintenance tasks, especially when table structures or loading patterns are not optimized. Poor clustering key choices, unordered data loads, or frequent full-table replacements are common drivers of unnecessary Auto-Clustering activity.
Billing model
The pricing dimensions that drive this cost.
- Automatic Clustering runs on Snowflake-managed serverless compute rather than customer warehouses and is billed in credits under the Auto Clustering service type; resource monitors cannot cap it
- Clustering Classic (tables that were already clustered before September 1, 2026) bills for the serverless compute used to recluster, so the more DML changes a table receives, the higher its maintenance cost
- Optima Clustering (tables newly clustered from September 1, 2026) bills per uncompressed GB ingested multiplied by an overlap factor: updates that change clustering key values are billed at the full rate, while append-only loads that arrive well clustered cost little
- Changing a clustering key triggers a one-time clustering cost, and reclustering can add storage cost when it increases Fail-safe storage
How to detect
3 checks to find it in your estate.
- Review Auto-Clustering activity metrics to identify tables with large volumes of data reclustered relative to total table size (e.g., >30-40% of the table re-clustered monthly)
- Analyze loading patterns for high-churn behaviors such as frequent bulk inserts, updates, or deletes
- Evaluate clustering key configurations to determine if keys align with actual query filter and join patterns
Assess whether tables experiencing high churn are critical for business performance or could tolerate less aggressive clustering
How to fix
4 ways to remove the waste.
- Optimize data loading practices by using incremental loads and pre-sorting data where possible to minimize disruption to partition structures
- Redesign cluster key selections to prioritize columns commonly used in query filters and joins, limit the number of keys, and order by cardinality
- Disable or adjust clustering maintenance for low-value or rarely queried tables to reduce unnecessary overhead
- Periodically monitor clustering costs and modify configurations based on evolving query access patterns
Documentation
Vendor references for pricing and configuration.