Skill community advanced
Warehouse Clustering Advisor
Choose warehouse size, clustering keys, and caching — measured.
Advises on Snowflake/BigQuery/Redshift tuning: clustering keys, warehouse sizing, result caching, and the difference between a scan problem and a compute problem.
npx de-agent-platform add warehouse-clustering-advisor At a glance
| What | Choose warehouse size, clustering keys, and caching — measured. |
|---|---|
| Where | Data Warehouses · tech-snowflake · tech-bigquery · tech-databricks |
Learning objectives
- Separate scan inefficiency from compute inefficiency
- Choose a clustering key from predicate selectivity
- Right-size a virtual warehouse from queue time
Security scan
Last sweep 2026-10-24: 0 finding(s), 0 marked as examples.
Details
Warehouse Clustering Advisor
Diagnose first
- Query scans far more partitions than it needs → clustering/partition problem.
- Scan is optimal but the query waits → warehouse sizing or concurrency problem.
Clustering key choice
Pick the column that appears in the WHERE clause of the most expensive queries, with reasonable cardinality. Order matters: put the most selective first.
Right-sizing from queue time
If queue time >> execution time for short queries, scale out (more clusters), not up (bigger warehouse). Different problems, different knobs.
Registry stats
| Verification | community · Sep 17, 2026 |
|---|---|
| Completeness | 100 |
| Trust multiplier | ×0.75 |
| Composite | 36.5 · adequate |
| Freshness | 37 days since last source check |
| Difficulty | advanced |
| Version | 0.2.0 |
| License | Apache-2.0 |
| Security flags | 2 |
Did this solve your problem?
Warehouse Clustering Advisor