Active warehouses maintain a table data cache, improving subsequent query performance by reducing table reads.
Cache size scales with warehouse compute resources: larger warehouses have larger caches.
Suspending a warehouse drops the cache, potentially impacting initial query performance upon resumption.
Resumed warehouses rebuild the cache: queries benefit as the cache grows.
Consider this trade-off:
Suspend to save credits: immediate cost savings, but potentially slower initial queries.
Leave running to maintain cache: faster initial queries, but ongoing credit consumption.