Why virtual warehouses control compute independently in Snowflake - Visual Breakdown

Process Flow - Why virtual warehouses control compute independently

User Query Arrives

↓

Virtual Warehouse Receives Query

↓

Warehouse Allocates Compute Resources

↓

Query Executes Using Allocated Compute

↓

Results Returned to User

↓

Other Warehouse Receives Query

↓

Allocates Its Own Compute Independently

↓

Executes Query Separately

↓

Returns Results Independently

Each virtual warehouse in Snowflake manages its own compute resources independently, allowing multiple queries to run in parallel without affecting each other.

Execution Sample

Snowflake

CREATE WAREHOUSE WH1 WITH WAREHOUSE_SIZE = 'SMALL';
CREATE WAREHOUSE WH2 WITH WAREHOUSE_SIZE = 'MEDIUM';
-- Run query on WH1
USE WAREHOUSE WH1;
SELECT COUNT(*) FROM SALES;
-- Run query on WH2
USE WAREHOUSE WH2;
SELECT COUNT(*) FROM CUSTOMERS;

Two virtual warehouses run queries independently, each using its own compute resources.

Process Table

Step	Warehouse	Action	Compute Allocated	Query Status	Result
1	WH1	Start Query	Small Compute Cluster	Running	N/A
2	WH2	Start Query	Medium Compute Cluster	Running	N/A
3	WH1	Query Processing	Small Compute Cluster	Running	N/A
4	WH2	Query Processing	Medium Compute Cluster	Running	N/A
5	WH1	Query Complete	Small Compute Cluster	Completed	Count from SALES
6	WH2	Query Complete	Medium Compute Cluster	Completed	Count from CUSTOMERS

💡 Both warehouses complete their queries independently using their allocated compute resources.

Status Tracker

Variable	Start	After Step 2	After Step 4	Final
WH1 Compute	None	Small Cluster Allocated	Small Cluster Active	Small Cluster Released
WH2 Compute	None	Medium Cluster Allocated	Medium Cluster Active	Medium Cluster Released
WH1 Query Status	Idle	Running	Running	Completed
WH2 Query Status	Idle	Running	Running	Completed

Key Moments - 2 Insights

Why does WH2 start allocating compute only after WH1 has started its query?

Each warehouse allocates compute independently when it receives a query, so WH2 starts allocation when its query begins, as shown in steps 2 and 4 of the execution table.

Can WH1 and WH2 share compute resources during query execution?

No, each virtual warehouse controls its own compute independently, so they do not share resources, preventing one query from slowing down another (see compute allocation columns in execution table).

Visual Quiz - 3 Questions

Look at the execution table, what compute size does WH1 use during its query?

A Large Compute Cluster

B Medium Compute Cluster

C Small Compute Cluster

D No Compute Allocated

💡 Hint

Check the 'Compute Allocated' column for WH1 in steps 1 and 3.

At which step does WH2 start running its query?

A Step 2

B Step 3

C Step 1

D Step 4

💡 Hint

Look at the 'Query Status' column for WH2 in the execution table.

If WH1 was resized to 'LARGE', how would the execution table change?

A WH2's compute allocation would change to Large Compute Cluster

B WH1's compute allocation would show Large Compute Cluster

C Both warehouses would share Large Compute Cluster

D No change in compute allocation

💡 Hint

Compute allocation depends on warehouse size per warehouse, see 'Compute Allocated' column.

Concept Snapshot

Virtual warehouses in Snowflake manage compute independently.
Each warehouse allocates its own compute resources when running queries.
This allows multiple queries to run in parallel without interference.
Warehouse size determines compute power allocated.
Compute resources are released after query completion.

Full Transcript

In Snowflake, virtual warehouses control compute independently. When a query is sent to a warehouse, it allocates compute resources based on its size. Multiple warehouses can run queries at the same time without sharing compute. This means one warehouse's workload does not slow down another. After queries finish, compute resources are released. This design allows flexible, scalable, and isolated query processing.

Practice

1. Why do virtual warehouses in Snowflake control compute independently?

easy

A. To share compute resources evenly among all users

B. To allow multiple workloads to run without affecting each other

C. To reduce storage costs by combining compute

D. To limit the number of queries that can run simultaneously

Solution

1. Step 1: Understand the role of virtual warehouses

   Virtual warehouses provide compute resources for queries and run independently.

2. Step 2: Identify the benefit of independent control

   Independent control prevents one workload from slowing down others by isolating compute resources.

3. Final Answer:

   To allow multiple workloads to run without affecting each other -> Option B

4. Quick Check:

   Independent compute control = no workload interference [OK]

Hint: Think: separate engines run separately to avoid slowdowns [OK]

Common Mistakes:

• Confusing compute independence with storage sharing
• Assuming warehouses share compute resources
• Thinking compute control reduces storage costs

2. Which of the following is the correct way to suspend a virtual warehouse in Snowflake?

easy

A. ALTER WAREHOUSE my_wh SUSPEND;

B. SUSPEND WAREHOUSE my_wh;

C. ALTER WAREHOUSE my_wh SET SUSPEND = TRUE;

D. ALTER WAREHOUSE my_wh SUSPEND IMMEDIATE;

Solution

1. Step 1: Recall Snowflake syntax for suspending warehouses

   The correct command uses ALTER WAREHOUSE with SUSPEND.

2. Step 2: Check each option's syntax

   Invalid syntax includes extra keywords like IMMEDIATE, missing ALTER, or incorrect SET usage. The correct syntax is ALTER WAREHOUSE my_wh SUSPEND;.

3. Final Answer:

   ALTER WAREHOUSE my_wh SUSPEND; -> Option A

4. Quick Check:

   Correct suspend syntax = ALTER WAREHOUSE ... SUSPEND [OK]

Hint: Remember: ALTER WAREHOUSE ... SUSPEND is correct [OK]

Common Mistakes:

• Using SUSPEND without ALTER WAREHOUSE
• Trying to set SUSPEND as a property
• Using unnecessary keywords like IMMEDIATE

3. Given two virtual warehouses, WH1 and WH2, running queries simultaneously, what happens if WH1 is resized larger while WH2 continues running?

medium

A. WH2's compute resources are reduced automatically

B. Both warehouses share the new combined compute power

C. WH1's resize does not affect WH2's compute resources

D. WH2 is suspended until WH1 finishes resizing

Solution

1. Step 1: Understand independent compute control

   Each warehouse controls its own compute resources independently.

2. Step 2: Analyze the effect of resizing one warehouse

   Resizing WH1 affects only WH1; WH2 continues unaffected.

3. Final Answer:

   WH1's resize does not affect WH2's compute resources -> Option C

4. Quick Check:

   Independent compute means resizing one doesn't impact others [OK]

Hint: Resize affects only targeted warehouse, others run normally [OK]

Common Mistakes:

• Assuming compute resources are shared dynamically
• Thinking resizing pauses other warehouses
• Believing compute is pooled automatically

4. You tried to resume a suspended warehouse with the command RESUME WAREHOUSE my_wh; but got an error. What is the likely cause?

medium

A. The correct command is ALTER WAREHOUSE my_wh RESUME;

B. Warehouse names cannot contain underscores

C. You must use ALTER WAREHOUSE my_wh RESUME WAREHOUSE;

D. The warehouse is already running and cannot be resumed

Solution

1. Step 1: Check Snowflake syntax for resuming warehouses

   The correct command uses ALTER WAREHOUSE with RESUME keyword.

2. Step 2: Identify the error in the given command

   RESUME WAREHOUSE alone is invalid; must use ALTER WAREHOUSE my_wh RESUME;

3. Final Answer:

   The correct command is ALTER WAREHOUSE my_wh RESUME; -> Option A

4. Quick Check:

   Resume warehouse syntax = ALTER WAREHOUSE ... RESUME [OK]

Hint: Use ALTER WAREHOUSE ... RESUME to restart suspended warehouse [OK]

Common Mistakes:

• Using RESUME WAREHOUSE alone as a command
• Misnaming warehouses with invalid characters
• Trying to resume an already running warehouse

5. You have three virtual warehouses: WH_A, WH_B, and WH_C. WH_A is running a heavy ETL job, WH_B is idle, and WH_C runs light queries. To optimize costs and performance, which approach best uses independent compute control?

hard

A. Suspend WH_A and WH_C, run all queries on WH_B

B. Resize all warehouses to the same size to balance compute

C. Merge all warehouses into one to share compute and reduce costs

D. Resize WH_A larger, suspend WH_B, and keep WH_C small and running

Solution

1. Step 1: Use independent compute control to match workload needs

   Resize WH_A larger for heavy ETL, suspend idle WH_B to save costs, keep WH_C small for light queries.

2. Step 2: Avoid resizing all equally or merging warehouses

   Balancing sizes wastes resources; merging loses independent control benefits.

3. Final Answer:

   Resize WH_A larger, suspend WH_B, and keep WH_C small and running -> Option D

4. Quick Check:

   Match warehouse size to workload independently for best cost/performance [OK]

Hint: Adjust each warehouse size and state based on its workload [OK]

Common Mistakes:

• Making all warehouses the same size regardless of workload
• Suspending warehouses that are actively needed
• Trying to merge warehouses to save costs