Size MySQL HeatWave analytics nodes from compressed data volume and price the database, storage and cluster together.
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.
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.
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.
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.
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.