For installations where Snow Owl and Elasticsearch are co-located, we recommend the following hardware specifications for full read-write scenarios:
vCPU
8
8
Memory
32 GB
32 GB
I/O performance
>= 5000 IOPS SSD
>= 5000 IOPS SSD
Disk space
200 GB
200 GB
For installations where Snow Owl connects to a managed Elasticsearch cluster at elastic.co we recommend the following hardware specifications for full read-write scenarios:
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
vCPU
8 (compute optimized)
Memory
4 GB
I/O performance
handled by elastic.co
Disk space
180 GB
If Snow Owl is planned to be used for resource-intensive workloads (large code system upgrades, frequent classification of terminology, 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.
Once the required runtime terminology data is indexed and prepared for consumption, read instances of the server can be booted up by pointing to the same Elasticsearch cluster (running co-located to the write instance or remotely by elastic.co). These instances require way fewer hardware resources to operate and can heavily reduce the read load on the write instance when needed.
vCPU
2
2
Memory
2-4 GB
2-4 GB
I/O performance
Not required
Not required
Disk space
1 Gb
1 Gb
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):
Last updated
