Workload

Performance tuning & optimization for Redshift → Snowflake

Redshift tuning habits (DISTKEY/SORTKEY, VACUUM/ANALYZE, WLM queues) don’t translate. We tune Snowflake layout, query shapes, and warehouse posture so pruning works, credits stay stable, and refresh SLAs hold under real concurrency.

Book assessment Explore workloads

Quick answer

Redshift tuning habits (DISTKEY/SORTKEY, VACUUM/ANALYZE, WLM queues) don’t translate. We tune Snowflake layout, query shapes, and warehouse posture so pruning works, credits stay stable, and refresh SLAs hold under real concurrency.

Back to pair page

Context

Why this breaks

Redshift performance tuning is often encoded in physical design and platform operations: DISTKEY/SORTKEY choices, VACUUM/ANALYZE, and WLM behavior. After migration, teams keep Redshift-era query shapes and expect Snowflake to behave similarly—then costs spike and SLAs slip because Snowflake’s cost/perf model is different. In Snowflake, credit burn is driven by warehouse usage and scan footprint, and MERGE/apply workloads can become full-target scans without bounded scope. Common post-cutover symptoms:

  • Queries scan too much because predicates don’t prune effectively - Join-heavy reports reshuffle large datasets; BI latency increases - MERGE/apply jobs scan full targets; credit burn becomes unpredictable - BI refresh contends with batch loads without warehouse isolation - Improvements regress because there are no baselines or gates

Approach

How conversion works

  • Baseline top workloads: identify the most expensive and most business-critical queries/pipelines (dashboards, marts, incremental loads). - Diagnose root causes: pruning effectiveness, join patterns, large scans, and MERGE scope. - Tune data layout: pruning-friendly clustering where justified by access paths (not folklore). - Rewrite for bounded applies: staged apply, bounded MERGE scopes, and pruning-friendly predicates. - Warehouse posture: isolate batch vs BI warehouses, tune concurrency and sizing, and implement credit guardrails. - Regression gates: store baselines and enforce thresholds so improvements persist.

Coverage

Supported constructs

Representative tuning levers we apply for Redshift → Snowflake workloads.

SourceTargetNotes
DISTKEY/SORTKEY-era performance assumptionsPruning-first predicates + evidence-driven clusteringReplace physical tuning with scan-footprint reduction.
WLM queue and concurrency settingsWarehouse isolation + concurrency postureStabilize refresh SLAs under peak BI load.
UPSERT jobs and incremental loadsBounded MERGE scopes + staged applyAvoid full-target scans and unpredictable credit burn.
Repeated BI scansPre-aggregation/materialization strategyReduce repeated large scans and stabilize dashboards.
Vacuum/analyze maintenance habitsEvidence-based tuning via query/warehouse metricsUse baselines and regression gates instead of maintenance folklore.
Ad-hoc expensive queriesGovernance guardrails + regression gatesPrevent credit blowups from unmanaged changes.

Compare

How workload changes

TopicRedshiftSnowflakeNotes
Primary cost driverCluster utilization and WLM behaviorWarehouse credits + scan footprintPruning and bounded scans dominate credit burn.
Data layout impactDIST/SORT keys can hide suboptimal SQLClustering is optional and evidence-drivenUse clustering only when predicates/join keys justify it.
Incremental applyDELETE+INSERT UPSERT conventionsBounded MERGE/apply windowsCorrectness and cost depend on apply window design.
Concurrency planningWLM queues and limitsWarehouse isolation + concurrency policiesPeak BI refresh needs explicit warehouse posture.

Examples

Examples

Illustrative Snowflake optimization patterns after Redshift migration: enforce pruning-friendly filters, bound MERGEs, isolate warehouses, and store baselines for regression gates.

01_pruning_first.sql
-- Pruning-first query shape (avoid wrapping filter columns)
SELECT
  region,
  SUM(revenue) AS rev
FROM MART.FACT_ORDERS
WHERE EVENT_DATE BETWEEN DATE '2025-01-01' AND DATE '2025-01-31'
GROUP BY 1;
02_bounded_merge.sql
-- Bound MERGE scope to affected window
SET min_d = (SELECT MIN(TO_DATE(updated_at)) FROM STG_ORDERS);
SET max_d = (SELECT MAX(TO_DATE(updated_at)) FROM STG_ORDERS);

MERGE INTO MART.FACT_ORDERS t
USING STG_ORDERS s
ON t.id = s.id
AND TO_DATE(t.updated_at) BETWEEN $min_d AND $max_d
WHEN MATCHED THEN UPDATE SET
  t.status = s.status,
  t.amount = s.amount,
  t.updated_at = s.updated_at
WHEN NOT MATCHED THEN
  INSERT (id, status, amount, updated_at)
  VALUES (s.id, s.status, s.amount, s.updated_at);
03_baselines.sql
-- Store baselines for regression gates (simplified)
CREATE TABLE IF NOT EXISTS CONTROL.PERF_BASELINES (
  artifact_id STRING,
  captured_at TIMESTAMP_NTZ,
  runtime_ms NUMBER,
  credits NUMBER
);

Workload Assessment

Replace Redshift tuning with Snowflake-native pruning

We identify your highest-cost migrated workloads, tune pruning and apply windows, and deliver before/after evidence with regression thresholds—so performance improves and stays stable.

Book assessment

Avoid

Common pitfalls

  • Carrying over DIST/SORT thinking: assuming physical distribution patterns translate; Snowflake needs pruning-first predicates and evidence-driven clustering.
  • Clustering by folklore: clustering keys chosen without evidence from predicates/join keys.
  • Full-target MERGE: missing apply boundaries causes large scans and credit spikes.
  • No warehouse isolation: BI and batch share warehouses; tail latency and spend spikes follow.
  • Over-materialization: too many intermediates without controlling refresh cost.
  • No regression gates: performance improves once, then regresses silently.

Proof

Validation approach

  • Baseline capture: runtime, scan footprint, and credits for top queries/pipelines.
  • Pruning checks: confirm pruning-friendly predicates and reduced scan footprint on representative parameters.
  • Before/after evidence: demonstrate improvements in runtime and credit burn; document tradeoffs.
  • Correctness guardrails: golden queries and KPI aggregates ensure tuning doesn’t change semantics.
  • Regression thresholds: define alerts (e.g., +30% credits or +30% runtime) and enforce via CI or scheduled checks.
  • Operational monitors: dashboards for warehouse utilization, credit burn, failures, and refresh SLA adherence.

Execution

Migration steps

A sequence that improves performance while protecting semantics.

  1. 01

    Identify top cost and SLA drivers

    Rank queries and pipelines by credits, runtime, and business criticality (dashboards, batch windows). Select a tuning backlog with clear owners.

  2. 02

    Create baselines and targets

    Capture current Snowflake metrics (runtime, credit burn, scan footprint) and define improvement targets. Freeze golden outputs so correctness doesn’t regress.

  3. 03

    Tune layout and apply posture

    Apply evidence-driven clustering where beneficial and redesign apply windows so MERGEs are bounded and pruning remains effective.

  4. 04

    Rewrite for pruning and reuse

    Apply pruning-aware rewrites, reduce repeated large scans with materializations where needed, and scope MERGEs to affected windows.

  5. 05

    Warehouse posture and governance

    Isolate batch and BI warehouses, tune concurrency, and implement guardrails to prevent credit blowups from new queries.

  6. 06

    Add regression gates

    Codify performance thresholds and alerting so future changes don’t reintroduce high credit burn or missed SLAs. Monitor post-cutover metrics continuously.

FAQ

Frequently asked questions

Why did credits increase after moving from Redshift to Snowflake? +

Most often because DIST/SORT-era query shapes and UPSERT conventions translate into larger scans in Snowflake. We tune pruning-friendly predicates, bound MERGE scopes, and isolate warehouses to stabilize credit burn.

Do we need clustering everywhere? +

No. Clustering is most useful for large tables with stable, selective predicates. We use evidence from query patterns and scan behavior before recommending clustering keys.

Can you optimize MERGE/apply pipelines too? +

Yes. We scope MERGEs to affected windows, design staging boundaries, and validate performance with credit/runtime baselines to prevent unpredictable scans.

How do you prevent BI refresh from impacting batch pipelines? +

We isolate warehouses (or use workload-aware sizing and concurrency limits) so BI and batch don’t contend. Monitoring and regression gates catch credit spikes and SLA regressions early.

Optimization Program

Prevent credit blowups with regression gates

Get an optimization backlog, bounded apply patterns, and performance gates (credit/runtime thresholds) so future releases don’t reintroduce slow dashboards or high credit burn.

Book assessment
Book assessment