Hardware configuration when EMS and PostgreSQL run on different machines with no FortiGate connected
The following table shows the configurations when EMS and PostgreSQL (Postgres) run on different Linux server machines with no FortiGate connected and multitenancy disabled:
The following table shows the configurations when EMS and Postgres run on different Linux server machines with no FortiGate connected and multitenancy enabled with up to 20 sites:
|
Number of managed endpoints |
EMS server machine
|
Postgres server machine |
Suggested keep alive interval |
||
|---|---|---|---|---|---|
| Number of virtual CPUs | Memory (RAM) (in GB) |
Number of virtual CPUs |
Memory (RAM) (in GB) |
||
| 10000 to 20000 | 8 | 8 | 4 | 22 | 120 seconds |
| 20000 to 50000 | 16 | 10 | 8 | 28 | |
| 50000 to 75000 | 20 | 12 | 12 | 32 | |
| 75000 to 150000 | 26 | 16 | 18 | 54 | 180 seconds |
|
150000 to 250000 |
32 |
22 |
28 |
66 |
240 seconds |
The following table shows the configurations when EMS and Postgres run on different Linux server machines with no FortiGate connected and multitenancy enabled with up to 50 sites:
|
Number of sites |
Number of managed endpoints |
EMS server machine |
SQL server machine |
Suggested keep alive interval |
||
|---|---|---|---|---|---|---|
|
Number of virtual CPUs |
Memory (RAM) (in GB) |
Number of virtual CPUs |
Memory (RAM) (in GB) |
|||
|
50 |
Up to 100000 |
24 |
18 |
26 |
64 |
180 seconds |