# Suboptimal query routing | Cloud Efficiency Hub

Canonical: https://www.pointfive.co/efficiency-hub/inefficiencies/suboptimal-query-routing

Organizations may experience unnecessary Snowflake spend due to inefficient query-to-warehouse routing, lack of dynamic warehouse scaling, or failure...

By: Simar Arora

Updated: 2026-09-28

[Cloud Efficiency Hub](https://www.pointfive.co/efficiency-hub) 

# Suboptimal Query Routing

The short version

Organizations may experience unnecessary Snowflake spend due to inefficient query-to-warehouse routing, lack of dynamic warehouse scaling, or failure to consolidate workloads during low-usage periods.

[Simar Arora](https://www.linkedin.com/in/simarpreet-arora/)

Value Engineer - FinOps @ Snowflake

Snowflake service

[Snowflake Query Processing](https://www.pointfive.co/efficiency-hub/cloud-services/snowflake-query-processing)

Category

[Other](https://www.pointfive.co/efficiency-hub/service-category/other)

Reference

CER-0029

Type

Inefficient Architecture

## Explanation

Why the waste happens and who it affects.

Snowflake now offers Adaptive Warehouses (Enterprise Edition or higher, select regions), which handle sizing, scaling, and query routing automatically. Third-party platforms also offer solutions to address these inefficiencies:

- Sundeck enables highly customizable, SQL-based control over the query lifecycle through user-defined rules (Flows, Hooks, Conditions). Cost optimization techniques include adaptive warehouse routing, instant warehouse suspension, and off-peak consolidation. However, it requires users to maintain optimization logic manually.

- Keebo offers a fully automated AI-driven approach, dynamically tuning warehouse size, auto-suspend, and related compute settings without requiring manual query intervention. It prioritizes minimal operational effort with continuous background optimization.

Choosing between these solutions depends heavily on the organization's internal capabilities and desired balance between control and automation.

## Billing model

The pricing dimensions that drive this cost.

- Standard virtual warehouses bill credits per second while running, with a 60-second minimum each time a warehouse starts or resumes; each step up in size roughly doubles the credits billed per hour

- Multi-cluster warehouses bill each running cluster at the warehouse size, so credits consumed per hour depend on how many clusters are running

- Adaptive Warehouses use query-based billing, where each query's cost depends on the compute and software resources it uses and the warehouse total is the sum of its queries

- Routing queries to oversized warehouses, or keeping extra warehouses and clusters running during low-usage periods, is what drives unnecessary credit consumption

## How to detect

4 checks to find it in your estate.

- Assess whether query workloads are currently routed manually or rely on static warehouse assignments

- Review warehouse utilization patterns to identify opportunities for dynamic resizing, load balancing, or consolidation during off-peak periods

- Evaluate whether internal teams have the expertise and capacity to manage custom query optimization rules

- Consider whether an AI-driven optimization platform would better fit organizational needs for cost reduction with minimal manual overhead

## How to fix

5 ways to remove the waste.

- Implement customizable query lifecycle management platforms (e.g., Sundeck) if granular control is required and in-house SQL/DevOps expertise is available

- Before adopting a third-party tool, evaluate Snowflake Adaptive Warehouses (native automatic sizing and query routing) and multi-cluster warehouses

- Deploy AI-driven warehouse optimization platforms (e.g., Keebo) for organizations prioritizing ease of use and autonomous cost management

- Pilot third-party solutions in a limited environment to validate cost savings and performance impacts before full-scale adoption

- Continuously monitor optimization effectiveness and adjust platform configurations based on workload evolution and business priorities

## Documentation

Vendor references for pricing and configuration.

- [Overview of warehouses  docs.snowflake.com](https://docs.snowflake.com/en/user-guide/warehouses-overview)

- [Understanding compute cost  docs.snowflake.com](https://docs.snowflake.com/en/user-guide/cost-understanding-compute)

- [Multi-cluster warehouses  docs.snowflake.com](https://docs.snowflake.com/en/user-guide/warehouses-multicluster)

- [Adaptive Compute  docs.snowflake.com](https://docs.snowflake.com/en/user-guide/warehouses-adaptive)

## Related inefficiencies

[Browse the library](https://www.pointfive.co/efficiency-hub)

- Snowflake Query Processing  CER-0112

### [Inefficient Execution of Repeated Queries](https://www.pointfive.co/efficiency-hub/inefficiencies/inefficient-execution-of-repeated-queries)

Inefficient execution of repeated queries occurs when common query patterns are frequently executed without optimization. Even if individual executions are successful, repeated inefficiencies compound overall compute consumption and credit...

Compute

- Snowflake Query Processing  CER-0515

### [Excessive Snowflake Cloud Services Consumption from Metadata-Heavy Operations](https://www.pointfive.co/efficiency-hub/inefficiencies/excessive-snowflake-cloud-services-consumption-from-metadata-heavy-operations)

The Snowflake cloud services layer handles authentication, metadata management, query compilation and optimization, and request caching. Its usage is free only up to 10% of the account's daily virtual warehouse usage; anything above that...

Compute

- Snowflake Tasks and Pipelines  CER-0025

### [Inefficient Pipeline Refresh Scheduling](https://www.pointfive.co/efficiency-hub/inefficiencies/inefficient-pipeline-refresh-scheduling)

Inefficient pipeline refresh scheduling occurs when data refresh operations are executed more frequently, or with more compute resources, than the actual downstream business usage requires. Without aligning refresh frequency and resource...

Other

---
Source: the public page above. Product screenshots and illustrative interfaces are examples, not live customer data.

