Comparison
Capacity planningvsWarehouse sizing
Capacity planning
you work out from load tests how much traffic one instance handles, and how many you need for Black Friday.
Determining the resources required to meet demand at a target latency, with headroom for failure and spikes. It requires a measured per-instance capacity, not an assumed one. Plan for the loss of a zone or a region as well as the peak, or your headroom disappears exactly when you need it.
Full entry →Warehouse sizing
you doubled the warehouse size, the query took half as long, and the bill was identical.
Choosing how much compute a workload gets, on a platform where cost is usually size multiplied by time. For a query that parallelises cleanly, a bigger warehouse is cost-neutral and finishes sooner; for one bottlenecked on a single skewed task it is pure waste. Sizing is therefore diagnostic — if doubling the size does not halve the time, the problem is skew or spill, and no amount of compute will fix it.
Full entry →