Elasticsearch Add-On for Heroku default provider instance configurationsedit

Elasticsearch data nodes are available in these configurations:

  • highio - Optimized for balanced RAM/vCPU/disk ratios and performance.
  • highstorage - Optimized for cost effective storage.
  • highcpu - Optimized for higher CPU performance compared to highio types.
  • highmem - Optimized for lower cost with lower storage ratio.

The following table contains the specific hardware for each cloud provider.

Instance configuration Provider Preferred Instance Type or Machine Configuration1 Storage Type1 Disk:Memory Ratio2

highio

AWS

i3

NVME

30:1

Azure

l32sv2

NVME

30:1

GCP

16 cores, 104 GB memory, 3000 GB storage

NVME

30:1

highstorage

AWS

d2

HDD

160:1

Azure

e16sv3

Standard Managed Disks (HDD)

160:1

GCP

22 cores, 140 GB memory, 20972 GB storage

Standard persistent disks (HDD)

160:1

highcpu

AWS

m5

EBS

8:1

Azure

d64sv3

Standard SSD

8:1

GCP

64 cores, 270 GB memory, 2250 GB storage

Local SSD

8:1

highmem

AWS

r4

EBS

2:1

Azure

e16sv3

Standard SSD

2:1

GCP

22 cores, 140 GB memory, 375 GB storage

Local SSD

2:1

Additional instancesedit

Instance configuration Provider Preferred Instance Type or Machine Configuration1 Storage Type1 Disk:Memory Ratio2

apm

AWS

r4

EBS

2:1

Azure

e32sv3

Standard SSD

2:1

GCP

22 cores, 140 GB memory, 375 GB storage

Local SSD

2:1

appsearch or enterprisesearch

AWS

m5

EBS

2:1

Azure

d64sv3

Standard SSD

2:1

GCP

64 cores, 270 GB memory, 2250 GB storage

Local SSD

8:1

ccs

AWS

r4

EBS

2:1

Azure

e32sv3

Standard SSD

2:1

GCP

22 cores, 140 GB memory, 375 GB storage

Local SSD

2:1

coordinating

AWS

m5

EBS

2:1

Azure

d64sv3

Standard SSD

8:1

GCP

64 cores, 270 GB memory, 2250 GB storage

Local SSD

8:1

kibana

AWS

r4

EBS

2:1

Azure

e32sv3

Standard SSD

2:1

GCP

22 cores, 140 GB memory, 375 GB storage

Local SSD

2:1

master

AWS

r4

EBS

2:1

Azure

e32sv3

Standard SSD

2:1

GCP

22 cores, 140 GB memory, 375 GB storage

Local SSD

2:1

ml

AWS

m5

EBS

2:1

Azure

d64sv3

Standard SSD

2:1

GCP

64 cores, 270 GB memory, 2250 GB storage

Local SSD

2:1

1 Preferred instance and storage types are subject to provider availability. To learn more about our provider instances, see AWS, Azure, and GCP reference pages.

2 Ratios are estimations.

JVM Heapedit

Memory sizes ensure efficient hardware utilization and might not scale to the power of two (n2). For sizes above 58, 60 or 64 GB (depending on instance type), we create multiple instances or nodes to ensure efficient JVM heap sizes. For example: If you provision a deployment with a 128 GB Elasticsearch cluster, two 64 GB nodes get created. To learn more about why we offer these JVM heap sizes, see Heap: Sizing and Swapping.