Question

An analyst runs an aggregation query at 9:00 AM and it completes in 45 seconds. A colleague runs the exact same query text at 9:20 AM using a different (but currently suspended) warehouse, and it returns results in under one second without resuming any warehouse. No underlying data changed between the two runs. Which Snowflake feature is responsible for this behavior?

Accepted Answer

The result cache in the cloud services layer returned the previously computed results

Answer

The warehouse local disk (data) cache retained the query's micro-partitions

Answer

The metadata cache returned min/max statistics without scanning data

Answer

The query acceleration service offloaded the scan to serverless compute