snowflake-load-scale

name	snowflake-load-scale
description	Implement Snowflake load testing, warehouse scaling, and capacity planning. Use when testing query performance at scale, configuring multi-cluster warehouses, or planning capacity for production Snowflake workloads. Trigger with phrases like "snowflake load test", "snowflake scale", "snowflake capacity", "snowflake benchmark", "snowflake multi-cluster".
allowed-tools	Read, Write, Edit, Bash(python3:*), Bash(snowsql:*)
version	1.5.0
license	MIT
author	Jeremy Longshore <[e-mail]>
tags	["saas","data-warehouse","analytics","snowflake"]
compatibility	Designed for Claude Code

Snowflake Load & Scale

Overview

Load testing, scaling strategies, and capacity planning for Snowflake workloads using warehouse sizing, multi-cluster configuration, and concurrent query simulation.

Scaling Model

Dimension	How to Scale	When
Single query speed	Scale UP (bigger warehouse)	Complex queries, large scans
Concurrent queries	Scale OUT (multi-cluster)	Many users, dashboard refresh
Data volume	Scale UP + clustering	Tables > 1TB
Mixed workloads	Separate warehouses	ETL + analytics on same data

Instructions

Step 1: Benchmark Current Performance

-- Baseline metrics for critical queries
-- Run each query 3 times and record results

-- Disable result cache for accurate benchmarking
ALTER SESSION SET USE_CACHED_RESULT = FALSE;

-- Test query 1: Point lookup
SELECT * FROM orders WHERE order_id = 12345;

-- Test query 2: Aggregation
SELECT DATE_TRUNC('month', order_date) AS month,
       COUNT(*) AS orders, SUM(amount) AS revenue
FROM orders
WHERE order_date >= '2025-01-01'
GROUP BY month ORDER BY ;


 c.name, (o.amount)  total_spend
 customers c
 orders o  c.id  o.customer_id
 o.order_date  DATEADD(days, , ())
  c.name
  total_spend 
LIMIT ;


 query_id, query_text, warehouse_name, warehouse_size,
       total_elapsed_time    seconds,
       bytes_scanned    gb_scanned,
       rows_produced, partitions_scanned, partitions_total,
       bytes_spilled_to_local_storage, bytes_spilled_to_remote_storage
 (INFORMATION_SCHEMA.QUERY_HISTORY_BY_SESSION())
  start_time 
LIMIT ;


 SESSION  USE_CACHED_RESULT  ;