Custos do Snowpipe¶
Com o modelo computacional sem servidor do Snowpipe, os usuários podem iniciar um carregamento de qualquer tamanho sem gerenciar um warehouse virtual. Em vez disso, o Snowflake fornece e gerencia os recursos computacionais, aumentando ou diminuindo automaticamente a capacidade com base no carregamento atual do Snowpipe.
Importante
Snowpipe ingestion is billed based on a fixed credit amount per GB. This simplified model provides you with more predictable data-loading expenses and simplifies cost estimation. The former cost model had two components: the actual compute resources used to load data, measured per-second/per-core, and a per-1,000-files charge.
This credit-per-GB billing model applies to all Snowflake editions: Standard, Enterprise, Business Critical, and Virtual Private Snowflake (VPS).
Para arquivos de texto (como CSV, JSON e XML), a cobrança é feita com base no tamanho não compactado. Para arquivos binários (como Parquet, Avro e ORC), a cobrança é feita com base no tamanho observado, independentemente da compactação.
Para mais informações, consulte a Tabela de consumo de serviços do Snowflake.
Consumo de recursos e sobretaxa de gerenciamento¶
With the credit-per-GB pricing model, Snowpipe billing is calculated based on a fixed credit amount per GB of data that you loaded. This simplified approach means that you don’t need to track or manage compute utilization, which was formerly measured with per-second/per-core granularity.
File sizes and staging frequency might impact the performance of Snowpipe. For recommended best practices, see Carregamentos contínuos de dados (ou seja, Snowpipe) e dimensionamento de arquivo.
Estimativa das taxas do Snowpipe¶
Estimating Snowpipe charges is straightforward. You can calculate your expected costs by using your anticipated data volume and the fixed credit amount per GB. Because text files — such as CSV, JSON, XML — are charged based on their uncompressed size, you must know the compression ratio of your text files.
You can verify these calculations against your actual usage by examining the BILLED_BYTES column in the relevant Account Usage views. The BILLED_BYTES column was introduced in the 2025_05 BCR bundle.
To understand the actual credit consumption for your specific workloads, we suggest that you experiment by performing a typical set of loads.
Visualização do histórico de carregamento de dados e custo¶
Account administrators (users with the ACCOUNTADMIN role) or users with a role granted the MONITOR USAGE global privilege can use Snowsight or SQL to view the credits billed to your Snowflake account within a specified date range.
Ocasionalmente, o processo de compactação e manutenção de dados pode consumir créditos do Snowflake. Por exemplo, os resultados retornados podem mostrar que você consumiu créditos com 0 BYTES_INSERTED e 0 FILES_INSERTED. Isto significa que seus dados não estão sendo carregados, mas o processo de compactação e manutenção dos dados consumiu alguns créditos.
Para ver os créditos faturados pelo carregamento de dados do Snowpipe para sua conta:
- Snowsight:
No menu de navegação, selecione Admin » Cost management.
- SQL:
Consulte um dos seguintes:
Função de tabela PIPE_USAGE_HISTORY (no Snowflake Information Schema).
Exibição PIPE_USAGE_HISTORY (em Account Usage).
You can run the following queries against the PIPE_USAGE_HISTORY view. You can verify costs based on volume by using the
BYTES_BILLEDcolumn.Consulta: Histórico de custos do Snowpipe (por dia, por objeto)
The following query provides a full list of pipes and the volume of credits that you consumed through the service over the last 30 days, broken out by day.
SELECT TO_DATE(start_time) AS date, pipe_name, SUM(credits_used) AS credits_used, SUM(bytes_billed) AS bytes_billed_total FROM snowflake.account_usage.pipe_usage_history WHERE start_time >= DATEADD(month,-1,CURRENT_TIMESTAMP()) GROUP BY 1,2 ORDER BY bytes_billed_total DESC;Consulta: Histórico do Snowpipe e média de m dias
Essa consulta mostra a média de créditos diários consumidos pelo Snowpipe, agrupados por semana ao longo do último ano. Essa consulta pode ajudar você a identificar anomalias nas médias de consumo diário ao longo do ano, para investigar aumentos súbitos ou mudanças inesperadas no consumo.
WITH credits_by_day AS ( SELECT TO_DATE(start_time) AS date, SUM(credits_used) AS credits_used, SUM(bytes_billed) AS bytes_billed_total FROM snowflake.account_usage.pipe_usage_history WHERE start_time >= DATEADD(year,-1,CURRENT_TIMESTAMP()) GROUP BY 1 ) SELECT DATE_TRUNC('week',date), AVG(credits_used) AS avg_daily_credits, AVG(bytes_billed_total) AS avg_daily_bytes_billed FROM credits_by_day GROUP BY 1 ORDER BY 1;
Nota
Monitores de recursos fornecem controle sobre o uso de crédito do warehouse virtual; no entanto, não é possível usá-los para controlar o uso de crédito para os warehouses fornecidos pelo Snowflake, incluindo o warehouse
SNOWPIPE.