Spilled to Remote StorageWarehouse · easy · ~10 minThe weekly customer-ranking query went from 4 minutes to 52. The profile shows a giant window function — ROW_NUMBER() OVER (ORDER BY lifetime_value DESC) across the ENTIRE 1.2B-row customer_events rollup — spilling 210GB to local disk and 84GB to remote storage. The team's proposed fix: 'run it on a 4XL'.There's a cheaper order of operations. Find it.Evidence

Query Profile

Profile Detail

Config

Checkpoints

What is the spill telling you, mechanically?

The cheap fix hiding in the query?

When IS resizing the right answer for spills, and how do you frame the decision? Interview-style.