Home
Product
Overview
Architecture
low latency
FAST INGESTION
mixed workloads
Low Latency
elt
Mixed workloads
elasticity
DATA SECURITY
CASE STUDIES
Is Firebolt right for Me
Knowledge Center
Docs
Pricing
RESOURCES
company
Contact us
HANDS-ON WORKSHOP
Each cluster can be scaled in single-node increments from 1-128. Additionally, each Engine can scale from 1-10 clusters to address concurrency requirements.
Pay for FBUs (Firebolt Units) consumed with second accuracy.
Start with a single node ‘S’ type engine and scale in one-node increments up to 128.
Ingestion requires a single node engine with node type S that runs for 6 minutes every hour. Node type S consumes 8 FBUs/hour.
6 min
BI workloads run at infrequent intervals with extended idle periods. We launch an engine of node type M. On average, this workload runs for 10 minutes each hour, with 5 minutes of idle time.
10 min
5 min idle
45 min stopped
10 min
ELT workload runs on an engine with a single S node (8 FBUs/hr) for 10 minutes every hour. This ELT workload scales out to 4 S nodes (32 FBUs/hr) once a day for a period of an hour.
10 min
5 min idle
5 min idle
60 min
10 min
The baseline engine is a 2-node cluster of S type nodes that runs 24 x 7. To address high concurrency, this engine adds another 2-node cluster from 9am - 5pm.
Cluster 2 (9am - 5pm)
Cluster 1 (24x7)
Firebolt Unit is a normalized rate of consumption, such that consumption scales linearly with the capacity of your engine across all three dimensions: type of node, number of nodes, and number of clusters; consumption is proportional to the FBU of the engine and the run time. Thanks to Firebolt’s multidimensional scaling, per-second billing, and auto-stop/start capabilities, compute consumption can be a fraction of a minute. FBU eliminates the need to keep track of individual node types, nodes, and the number of clusters. There’s no binding to specific instance types, so you are free to use pre-paid credits on any node type.
While FBUs measure consumption, the performance profile of a workload depends on the engine topology.
Each node type consumes a specified number of FBUs. Compute consumption is billed in one-second increments. For example, a type ‘M’ node consumes 16 FBUs. The same node running for one minute will consume FBU-hour calculated as such: Consumed FBU-hours = (Engine FBU) (1 hour / 3600 seconds) x ( 60 seconds) = (16/3600) x 60 = 0.27 FBU-hours.
Consumption starts when the engine endpoint is available for querying.
US East (Virginia), US West (Oregon) and EU (Frankfurt)
Yes, commitment based discounts are available. Contact our sales team for more information.
Firebolt provides multidimensional scaling to help right-size workloads. Autostop and Autostart are features that help reduce costs by eliminating idle time. Firebolt also provides global visibility of consumption and costs through built-in organizational governance and account-level consumption breakdown.
Firebolt provides engine consumption and spend information in the Web UI. Additionally, granular engine-level consumption can be found via the information_schema.engine_metering_history view that details the hourly consumption of all the engines within an account. Users can also drill down into how the topology of their engines (node type, number of nodes and number of clusters) was modified over time, providing visibility into the FBU consumption of their engines.
%20logo.png){kind=icon}
