Push redirector server sizing
The following table provides recommended sizing for the servers that host the push redirector.
Push servers are lightweight and typically sized similarly to your servers, effectively doubling the number of servers in your web tier.
Note: While a typical deployment uses a server-per-region approach (see
below), it is possible to configure multiple push redirectors to listen on
different ports on a single host.
| Region | Server | CPU | RAM | Disk | Notes |
|---|---|---|---|---|---|
| PROD | VM1 | 2 | 4 GB | 50 GB | Two VMs on physically redundant hosts located in different data centres. Each VM can service the entire production volume. |
| PROD | VM2 | 2 | 4 GB | 50 GB | Two VMs on physically redundant hosts located in different data centres. Each VM can service the entire production volume. |
| STAGE | VM3 | 2 | 4 GB | 50 GB | At least one region should mirror the PROD configuration. To configure multiple push redirectors to run on one VM, you require an additional 2 GB of RAM per push redirector instance. It is possible to run multiple VMs on one physical host. |
| STAGE | VM4 | 2 | 4 GB | 50 GB | At least one region should mirror the PROD configuration. To configure multiple push redirectors to run on one VM, you require an additional 2 GB of RAM per push redirector instance. It is possible to run multiple VMs on one physical host. |
| QA | VM5 | 1 | 4 GB | 30 GB | One VM per environment in the lower regions. |
| DEV | VM6 | 1 | 4 GB | 30 GB | One VM per environment in the lower regions. |