MySQL HeatWave Database Service Pricing

MySQL HeatWave on OCI and AWS

MySQL HeatWave on OCI

MySQL HeatWave

Product
Comparison price (/vCPU)*
Unit price
Unit
MySQL Database - ECPU


ECPU Per Hour
Oracle Cloud Infrastructure - HeatWave


HeatWave capacity per hour
Oracle Cloud Infrastructure - HeatWave - Storage


Gigabyte storage capacity per month
MySQL Database—Storage


Gigabyte storage capacity per month
MySQL Database—Backup Storage


Gigabyte storage capacity per month
MySQL Database - Outbound Data Transfer - Inter OCI Region


Gigabyte Outbound Data Transfer Per Month
MySQL Database—Standard - AMD E4 - Compute


OCPU per hour
MySQL Database—Standard - AMD E4 - Memory


Gigabyte per hour
MySQL Database—Standard - Intel X9 - Compute


OCPU per hour
MySQL Database—Standard - Intel X9 - Memory


Gigabyte per hour
MySQL Database—Optimized - Intel X9 - Compute


OCPU per hour
MySQL Database—Optimized - Intel X9 - Memory


Gigabyte per hour
MySQL Database for HeatWave—Standard


Node per hour
MySQL Database for HeatWave—Bare Metal Standard


Node per hour
HeatWave—Standard


Node per hour
  • *To make it easier to compare pricing across cloud service providers, Oracle web pages show both vCPU (virtual CPUs) prices and OCPU (Oracle CPU) prices for products with compute-based pricing. The products themselves, provisioning in the portal, billing, etc. continue to use OCPU (Oracle CPU) units. OCPUs represent physical CPU cores. Most CPU architectures, including x86, execute two threads per physical core, so 1 OCPU is the equivalent of 2 vCPUs for x86-based compute. The per-hour OCPU rate customers are billed at is therefore twice the vCPU price since they receive two vCPUs of compute power for each OCPU, unless it's a sub-core instance such as preemptible instances.

Small configuration


SCENARIO

A marketing agency wants to analyze advertising campaign performance in real-time. 200 GB of data.

SPECS

  • 1 MySQL.2 – 2 ECPU, 16GB memory
  • 4 HeatWave.32GB – 32 GB memory
  • MySQL Database Storage – 200 GB

ESTIMATED MONTHLY COST
US$ 127.93

Medium configuration


SCENARIO

A telecommunications company wants to analyze its customers’ communication patterns in real-time. 4 TB of data.

SPECS

  • 1 MySQL.8 – 8 ECPU and 64 GB memory
  • 4 HeatWave.512GB – 512 GB memory
  • MySQL Database Storage – 4 TB

ESTIMATED MONTHLY COST
US$ 1,425.40

Large configuration


SCENARIO

An automotive company wants to obtain real-time telemetry analytics. 30 TB of data.

SPECS

  • MySQL.32 - 32 ECPU and 256 GB memory
  • 30 HeatWave.512GB – 512 GB memory
  • MySQL Database Storage – 30 TB

ESTIMATED MONTHLY COST
US$ 9,928.01

MySQL HeatWave on AWS

Currently available from North America, Europe, Japan, and India.

ECPU (Elastic CPU) per hour is defined as a combination of the total CPU hours used by MySQL Database and a measure of work done by the MySQL Database and HeatWave. HeatWave capacity per hour is defined as a unit of 16 gigabyte memory hours allocated in MySQL HeatWave.

MySQL HeatWave on AWS

Product
Unit price
Unit
HeatWave—AWS

HeatWave capacity per hour
MySQL Database—AWS—ECPU

ECPU per hour
MySQL Database—AWS—storage

Gigabyte storage capacity per month
MySQL Database—AWS—backup storage

Gigabyte storage capacity per month
MySQL Database—AWS—outbound data transfer—inter AWS region

Gigabyte of data transferred
MySQL Database—AWS—outbound data transfer—to internet

Gigabyte of data transferred

Small configuration


SCENARIO

A municipality is launching a new application to conduct various surveys and wants to run real-time analytics on the data. 50GB of data.

SPECS

  • 1 MySQL Database node - 1 ECPU (2 vCPUs) and 16 GB memory
  • 2 HeatWave nodes – 16 GB memory
  • MySQL Database Storage – 50 GB

ESTIMATED MONTHLY COST
US$ 116

Medium configuration


SCENARIO

A marketing agency wants to analyze advertising campaign performance in real-time. 1 TB of data.

SPECS

  • MySQL Database node - 4 ECPUS (8 vCPUs) and 64 GB memory
  • 3 HeatWave nodes – 256 GB memory
  • MySQL Database Storage – 1 TB

ESTIMATED MONTHLY COST
US$ 2,028

Large configuration


SCENARIO

A telecommunications company wants to analyze its customers’ communication patterns in real-time. 10 TB of data.

SPECS

  • 1 MySQL Database node - 16 ECPUS (32 vCPUs) and 256 GB memory
  • 25 HeatWave nodes – 256 GB memory
  • MySQL Database Storage – 10 TB

ESTIMATED MONTHLY COST
US$ 16,486