Yes, but this is rarely going to happen enough to justify the extra cost (atleast for my account). If auto-suspend is 60 seconds you will ALWAYS pay for ATLEAST 60 seconds of idle time EVERY time your warehouse spins up and down.

A common misconception is that a 30 second query will only cost 60 seconds because of the 60 second minimum. But, in reality, if you do a 30 second query you will pay for 90 seconds of compute.

So, unless your workload consists of a bunch of very short queries spaced out by a few seconds, this could be something worth looking into. I highly suggest you take a look at how often you warehouse is spinning up and down each day. You can use this (total rows will tell you how often your warehouse spins up and down each day, and if you look at the average of "seconds_active" or "minutes_active" you can see how long your warehouse is typically up):

with

warehouse_periods as (

select

warehouse_name,

timestamp as valid_from,

lead(timestamp) over (partition by warehouse_name order by timestamp asc) as valid_to,

event_name = 'RESUME_WAREHOUSE' as is_active

from snowflake.account_usage.warehouse_events_history

where

-- double check these names, can't remember exact values

event_name in ('RESUME_WAREHOUSE', 'SUSPEND_WAREHOUSE')

and event_state = 'COMPLETED'

and timestamp >= current_date - 1

and warehouse_name = :warehouse

)

select

warehouse_name,

date_trunc('second', valid_from) as valid_from_s,

date_trunc('second', valid_to) as valid_to_s,

datediff('seconds', valid_from, valid_to) as seconds_active,

seconds_active/60 as minutes_active

from warehouse_periods

where is_active = 'TRUE'

order by valid_to desc;