Snow Owl Docs
9.x
9.x8.x7.x6.xv7.16.0v7.15.0v7.14.0v7.13.0v7.12.0v7.11.0v7.10.0v7.9.0v7.8.0v7.7.0v7.6.0v7.5.1v7.5.0v7.4.0v7.3.0v7.2.0v7.1.0v7.0.1v7.0.0
9.x
9.x8.x7.x6.xv7.16.0v7.15.0v7.14.0v7.13.0v7.12.0v7.11.0v7.10.0v7.9.0v7.8.0v7.7.0v7.6.0v7.5.1v7.5.0v7.4.0v7.3.0v7.2.0v7.1.0v7.0.1v7.0.0
  • Introduction
  • Quick Start
    • Create your first Resource
    • Import SNOMED CT
    • Find concepts by ID or term
    • Find concepts using ECL
    • Next steps
  • Setup and Administration
    • Plan your deployment
      • Technology stack
      • Hardware requirements
      • Software requirements
    • Configuration
      • Release package
      • Folder structure
      • Get SSL certificate (optional)
      • Preload dataset (optional)
      • Configure Elastic Cloud (optional)
      • System settings
      • Spin up the service
    • Upgrade Snow Owl
    • Backup and restore
      • Backup
      • Restore
    • User management
    • Advanced installation methods
      • Install Snow Owl
        • Using an archive
        • Using RPM
        • Using DEB
      • System configuration
        • Disable swapping
        • File descriptors
        • Virtual memory
        • Number of threads
      • Configure Snow Owl
      • Start Snow Owl
      • Stop Snow Owl
    • Advanced configuration
      • Setting JVM options
      • Logging configuration
      • Elasticsearch configuration
      • Security
        • File realm
        • LDAP realm
  • Terminology Standards
    • SNOMED CT
      • Extensions and Snow Owl
      • Scenarios
        • Single Edition
        • Single Extension Authoring
        • Multi Extension Authoring
      • Development
      • Releases
      • Upgrading
    • LOINC
    • Socialstyrelsen Standards
      • ICD-10-SE
      • ICF
      • KVÅ (KKÅ/KMÅ)
  • Content syndication
  • REST APIs
    • FHIR API
      • CodeSystem
      • ValueSet
      • ConceptMap
    • Native API
      • Resource management
      • Content access
      • Content management
      • SNOMED CT API
        • Branching
        • Compare
        • Concepts
        • Reference Sets
  • Release notes
Powered by GitBook
On this page
  • Snow Owl with a co-located Elasticsearch cluster
  • Snow Owl with a managed Elasticsearch cluster
  • Cloud VMs
Export as PDF
  1. Setup and Administration
  2. Plan your deployment

Hardware requirements

Snow Owl with a co-located Elasticsearch cluster

For installations where Snow Owl and Elasticsearch are co-located, we recommend the following hardware specifications:

Snow Owl & co-located ES
Cloud
Dedicated

vCPU

8

8

Memory

32 GB

32 GB

I/O performance

>= 5000 IOPS SSD

>= 5000 IOPS SSD

Disk space

200 GB

200 GB

Snow Owl with a managed Elasticsearch cluster

For installations where Snow Owl connects to a managed Elasticsearch cluster at elastic.co we recommend the following hardware specifications:

Snow Owl
Cloud
Dedicated

vCPU

8 (compute optimized)

8

Memory

16 GB

16 GB

I/O performance

OS: balanced disk

TS file storage: local SSD

OS: HDD / SSD

TS file storage: SSD

Disk space

OS: 20 GB

TS file storage: 100 GB

OS: 20 GB

TS file storage: 100 GB

Elasticsearch @ elastic.co

vCPU

8 (compute optimized)

Memory

4 GB

I/O performance

handled by elastic.co

Disk space

180 GB

In case Snow Owl is planned to be used with resource-intensive workloads (large code system upgrades, frequent classification of terminologies, bulk authoring) an 8 vCPU / 4 GB Elasticsearch cluster might not be sufficient. Consider increasing the size of the hosted Elasticsearch instance gradually, so that finding the sweet spot will be straightforward.

Cloud VMs

Here are a few examples of which Virtual Machine types could be used for hosting the Terminology Server at the three most popular Cloud providers (including but not limited to):

Cloud Provider
VM type

GCP

AWS

Azure

Last updated 1 year ago

c2d-highcpu-8
c5d-2xlarge
F8s v2