Auto-suspend and auto-resume in Snowflake - Time & Space Complexity

Time Complexity: Auto-suspend and auto-resume

O(n)

Understanding Time Complexity

We want to understand how the time cost changes when Snowflake automatically pauses and resumes warehouses.

Specifically, how does this affect the number of operations as usage grows?

Scenario Under Consideration

Analyze the time complexity of auto-suspend and auto-resume behavior.

-- Warehouse is set to auto-suspend after 5 minutes
ALTER WAREHOUSE my_wh SET AUTO_SUSPEND = 300;

-- Warehouse is used by queries
SELECT * FROM my_table;

-- Warehouse auto-suspends after inactivity
-- Warehouse auto-resumes when new queries arrive

This sequence shows how the warehouse pauses when idle and starts again when needed.

Identify Repeating Operations

Look at what happens repeatedly during usage.

• Primary operation: Warehouse auto-suspend and auto-resume triggers
• How many times: Once per idle period followed by new query activity

How Execution Grows With Input

As the number of queries increases, the warehouse may suspend and resume multiple times.

Input Size (n)	Approx. Auto-suspend/Resume Cycles
10 queries	Few cycles if queries are close in time
100 queries	More cycles if queries are spread out with idle gaps
1000 queries	Many cycles if queries are intermittent with idle periods

Pattern observation: The number of suspend/resume cycles grows roughly with how often queries are separated by idle time.

Final Time Complexity

Time Complexity: O(n)

This means the number of suspend and resume operations grows linearly with the number of query bursts separated by idle time.

Common Mistake

[X] Wrong: "Auto-suspend and auto-resume happen only once regardless of query count."

[OK] Correct: Each time the warehouse is idle for the set period, it suspends, and each new query triggers a resume, so these operations happen multiple times as usage patterns vary.

Interview Connect

Understanding how auto-suspend and auto-resume scale helps you explain cost and performance trade-offs in cloud data warehouses.

Self-Check

"What if the auto-suspend time is set to zero (disabled)? How would the time complexity of suspend/resume operations change?"

Practice

1. What is the main purpose of the auto-suspend feature in a Snowflake warehouse?

easy

A. To increase the warehouse size during peak hours

B. To automatically start the warehouse when a query is submitted

C. To automatically stop the warehouse after a period of inactivity to save costs

D. To backup warehouse data automatically

Solution

1. Step 1: Understand auto-suspend functionality

   Auto-suspend stops the warehouse when it is idle for a set time to avoid unnecessary charges.

2. Step 2: Differentiate from auto-resume

   Auto-resume starts the warehouse when a query runs, not auto-suspend.

3. Final Answer:

   To automatically stop the warehouse after a period of inactivity to save costs -> Option C

4. Quick Check:

   Auto-suspend = stops warehouse after inactivity [OK]

Hint: Auto-suspend stops idle warehouse to save money [OK]

Common Mistakes:

• Confusing auto-suspend with auto-resume
• Thinking auto-suspend increases warehouse size
• Assuming auto-suspend backs up data

2. Which of the following is the correct way to enable auto-resume for a Snowflake warehouse using SQL?

easy

A. ALTER WAREHOUSE my_wh SET AUTO_RESUME = TRUE;

B. ALTER WAREHOUSE my_wh SET AUTO_SUSPEND = TRUE;

C. CREATE WAREHOUSE my_wh AUTO_RESUME = ON;

D. ALTER WAREHOUSE my_wh ENABLE AUTO_RESUME;

Solution

1. Step 1: Recall correct syntax for enabling auto-resume

   The correct command uses ALTER WAREHOUSE with SET AUTO_RESUME = TRUE.

2. Step 2: Eliminate incorrect options

   ALTER WAREHOUSE my_wh SET AUTO_SUSPEND = TRUE; sets auto_suspend, not auto_resume. CREATE WAREHOUSE my_wh AUTO_RESUME = ON; uses wrong syntax for CREATE. ALTER WAREHOUSE my_wh ENABLE AUTO_RESUME; uses invalid command.

3. Final Answer:

   ALTER WAREHOUSE my_wh SET AUTO_RESUME = TRUE; -> Option A

4. Quick Check:

   Enable auto-resume with SET AUTO_RESUME = TRUE [OK]

Hint: Use ALTER WAREHOUSE ... SET AUTO_RESUME = TRUE to enable [OK]

Common Mistakes:

• Confusing AUTO_RESUME with AUTO_SUSPEND
• Using CREATE instead of ALTER for existing warehouse
• Using invalid commands like ENABLE AUTO_RESUME

3. Given this SQL command sequence:

ALTER WAREHOUSE my_wh SET AUTO_SUSPEND = 300;
ALTER WAREHOUSE my_wh SET AUTO_RESUME = TRUE;
-- Warehouse is currently suspended
SELECT CURRENT_WAREHOUSE();

What happens when the SELECT query runs?

medium

A. The warehouse automatically resumes and the query runs successfully

B. The query fails because the warehouse is suspended

C. The warehouse remains suspended and query waits indefinitely

D. The warehouse resumes but the query returns NULL

Solution

1. Step 1: Understand auto-resume behavior

   With AUTO_RESUME = TRUE, the warehouse starts automatically when a query runs.

2. Step 2: Apply to the SELECT query

   The warehouse is suspended but will resume automatically before executing the SELECT.

3. Final Answer:

   The warehouse automatically resumes and the query runs successfully -> Option A

4. Quick Check:

   Auto-resume starts warehouse on query run [OK]

Hint: Auto-resume starts suspended warehouse on query execution [OK]

Common Mistakes:

• Assuming query fails if warehouse is suspended
• Thinking warehouse stays suspended during query
• Believing query returns NULL when warehouse resumes

4. You set AUTO_SUSPEND = 0 and AUTO_RESUME = TRUE on a warehouse. What issue might occur?

medium

A. The warehouse suspends and resumes repeatedly every second

B. The warehouse suspends immediately and never resumes

C. The warehouse suspends after default 60 seconds

D. The warehouse never suspends, causing continuous charges

Solution

1. Step 1: Understand AUTO_SUSPEND = 0 meaning

   Setting AUTO_SUSPEND to 0 disables auto-suspend, so warehouse stays running.

2. Step 2: Consider AUTO_RESUME effect

   AUTO_RESUME = TRUE allows auto-start but does not suspend warehouse automatically.

3. Final Answer:

   The warehouse never suspends, causing continuous charges -> Option D

4. Quick Check:

   AUTO_SUSPEND=0 disables suspend, warehouse runs always [OK]

Hint: AUTO_SUSPEND=0 means warehouse never suspends [OK]

Common Mistakes:

• Thinking AUTO_SUSPEND=0 suspends immediately
• Assuming warehouse suspends after default time
• Believing warehouse cycles suspend/resume every second

5. You want to minimize costs by suspending a warehouse after 5 minutes of inactivity but ensure it resumes automatically when needed. Which configuration is best?

hard

A. Set AUTO_SUSPEND = 60 and AUTO_RESUME = FALSE

B. Set AUTO_SUSPEND = 300 and AUTO_RESUME = TRUE

C. Set AUTO_SUSPEND = 0 and AUTO_RESUME = FALSE

D. Set AUTO_SUSPEND = 600 and AUTO_RESUME = TRUE

Solution

1. Step 1: Choose auto-suspend time for 5 minutes

   5 minutes equals 300 seconds, so AUTO_SUSPEND = 300 is correct.

2. Step 2: Enable auto-resume for automatic start

   Setting AUTO_RESUME = TRUE ensures warehouse starts when queries run.

3. Final Answer:

   Set AUTO_SUSPEND = 300 and AUTO_RESUME = TRUE -> Option B

4. Quick Check:

   5 min suspend + auto-resume = AUTO_SUSPEND=300 & AUTO_RESUME=TRUE [OK]

Hint: Use 300 seconds for 5 min suspend and enable auto-resume [OK]

Common Mistakes:

• Using 0 for AUTO_SUSPEND disables suspend
• Disabling AUTO_RESUME causes manual start
• Setting suspend time too short or too long