OCI MySQL HeatWave Calculator
Size MySQL HeatWave analytics nodes from compressed data volume and price the database, storage and cluster together.
About OCI MySQL HeatWave Calculator
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
Worked example
With the default values below, OCI MySQL HeatWave Calculator returns Monthly Cost of $1,035.12. Change any input above and every figure here is recalculated in your browser.
Inputs used
- MySQL ECPUsaccepts 1–512 ECPU
- 16 ECPU
- Price per MySQL ECPU-houraccepts 0–10 USD/ECPU-hour
- 0.0392 USD/ECPU-hour
- Database storageaccepts 50–1,000,000 GB
- 1,024 GB
- Storage price per GB-monthaccepts 0–5 USD/GB-month
- 0.0425 USD/GB-month
- Enable a HeatWave cluster
- Yes
- Data loaded into HeatWaveaccepts 0–1,000,000 GB
- 2,048 GB
- HeatWave compression ratioaccepts 1–10 ×
- 2 ×
- Memory per HeatWave nodeaccepts 32–2,048 GB
- 512 GB
- Price per HeatWave node-houraccepts 0–50 USD/hour
- 0.3528 USD/hour
- Billed hours per monthaccepts 1–744 hours
- 744 hours
Results
- 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
- Node Memory Utilisation
- 100.0%
- HeatWave Share of the Bill
- 50.7%
Step by step
- 1Values used
- 2OCI MySQL HeatWave
- 3Monthly Cost= 1,035.12
- 4MySQL Compute Charge= 466.64
- 5Storage Charge= 43.52
- 6HeatWave Cluster Charge= 524.97
- 7HeatWave Nodes Required= 2
- 8In-Memory Footprint After Compression= 1,024 GB
Assumptions and limits
- The result is derived only from the 10 inputs listed above. Anything not among them is not part of the calculation.
- In particular, this calculator does not take inflation, tax or compounding frequency into account.
- Figures are rounded for display to 2 decimal places, so totals built from several rounded parts can differ slightly from the unrounded arithmetic.
How these calculators are built and tested is described on the Methodology page. If a figure looks wrong, please report it.
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.