OCI MySQL HeatWave Calculator
Size MySQL HeatWave analytics nodes from compressed data volume and price the database, storage and cluster together.
Inputs
HeatWave holds data in memory in compressed form, typically 2× or better.
Monthly Cost
$1,035.12
MySQL Compute Charge
$466.64
Storage Charge
$43.52
HeatWave Cluster Charge
$524.97
HeatWave Nodes Required
2
In-Memory Footprint After Compression
1,024GB
Node Memory Utilisation
100.0%
HeatWave Share of the Bill
50.7%
Step by step
Values used
MySQL ECPUs = 16 ECPU; Price per MySQL ECPU-hour = 0.0392 USD/ECPU-hour; Database storage = 1,024 GB; Storage price per GB-month = 0.0425 USD/GB-month; Enable a HeatWave cluster = Yes; Data loaded into HeatWave = 2,048 GB; HeatWave compression ratio = 2 ×; Memory per HeatWave node = 512 GB; Price per HeatWave node-hour = 0.3528 USD/hour; Billed hours per month = 744 hours
OCI MySQL HeatWave
HeatWave nodes = ceil(data loaded ÷ compression ratio ÷ memory per node); monthly = ECPUs × ECPU rate × hours + GB × storage rate + nodes × node rate × hours.
Monthly Cost
= 1,035.12
MySQL Compute Charge
= 466.64
Storage Charge
= 43.52
HeatWave Cluster Charge
= 524.97
HeatWave Nodes Required
= 2
In-Memory Footprint After Compression
= 1,024 GB
How it works
HeatWave keeps the analytics data set entirely in memory, so the node count is driven by data volume divided by the compression ratio rather than by query load. A node that is only half full still bills in full, which means the last node added is the expensive one and a small reduction in loaded tables can remove it. The cluster is usually the largest line on a HeatWave bill, so knowing whether your data lands just under or just over a node boundary is worth more than any query tuning. Confirm the ECPU, storage and node-hour prices in the Oracle Cloud cost estimator for your region, and measure your real compression ratio rather than assuming it.
Formula
OCI MySQL HeatWave
HeatWave nodes = ceil(data loaded ÷ compression ratio ÷ memory per node); monthly = ECPUs × ECPU rate × hours + GB × storage rate + nodes × node rate × hours.
- compression ratio
- How much smaller the data is once loaded into HeatWave memory
- memory per node
- Usable in-memory capacity of one HeatWave node
- in-memory footprint
- Compressed size of the analytics data set
Frequently Asked Questions
How is OCI MySQL HeatWave calculated?
HeatWave nodes = ceil(data loaded ÷ compression ratio ÷ memory per node); monthly = ECPUs × ECPU rate × hours + GB × storage rate + nodes × node rate × hours. HeatWave keeps the analytics data set entirely in memory, so the node count is driven by data volume divided by the compression ratio rather than by query load. A node that is only half full still bills in full, which means the last node added is the expensive one and a small reduction in loaded tables can remove it.
Why does OCI MySQL HeatWave matter?
The cluster is usually the largest line on a HeatWave bill, so knowing whether your data lands just under or just over a node boundary is worth more than any query tuning. Confirm the ECPU, storage and node-hour prices in the Oracle Cloud cost estimator for your region, and measure your real compression ratio rather than assuming it.
What values do I need to enter?
This calculator takes 10 inputs: MySQL ECPUs, Price per MySQL ECPU-hour, Database storage, Storage price per GB-month, Enable a HeatWave cluster, Data loaded into HeatWave, HeatWave compression ratio, Memory per HeatWave node, Price per HeatWave node-hour, Billed hours per month. The pre-filled defaults are a realistic starting point — replace them with figures from your own environment for a result you can act on.