Sizing your deployment
When planning your on premises deployment, it's important to size your instances correctly. This document contains general guidance; if you have any questions, please contact us and our team will be happy to assist.
Application Instances
Polytomic runs as 3 different roles: the web interface, sync workers, and general workers. The same instances can fulfill multiple roles, but you can achieve higher throughput by deploying separate instances for each.
Role | Minimum CPU | Minimum RAM | Recommended Instances |
---|---|---|---|
| 1 VCPU | 1 Gi | 2 |
| 1 VCPU | 1 Gi | 1 |
| 1 VCPU | 2 Gi | 2 |
Utilization for web
and worker
roles are approximately fixed. The sync
role, however, can be sized based on expected sync volume. The sync volume is the number of records synced in a single execution.
Sync Volume | Recommended CPU | Recommended RAM |
---|---|---|
< 10k | 1 VCPU | 2 Gi |
< 100k | 1 VCPU | 4 Gi |
< 1MM | 2 VCPU | 6 Gi |
| 2 VCPU | 10 Gi |
Postgres
We recommend your Postgres instance to have at least 2 GB of memory, 2vCPUs, and 80GB of storage, though your database needs will depend heavily on sync volume.
If it’s on AWS or another managed platform that is easy to resize, getting the sizing correct is less important out of the box. However, if you’re rolling your own hardware or the instance is more difficult to upgrade, you may want to over-provision.
Updated 1 day ago