Fortinet white logo
Fortinet white logo

EMS Administration Guide

Hardware configuration when EMS and Postgres run on different machines with no FortiGate connected

Hardware configuration when EMS and Postgres 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:

Number of managed endpoints

EMS server machine

Postgres server machine

Suggested keep alive (KA) interval

Deployment duration

Number of virtual CPUs Memory (RAM) (in GB)

Number of virtual CPUs

Memory (RAM) (in GB)

10000 to 20000 8 6 4 16 120 seconds

1 to 2 days

20000 to 50000 16 8 6 22

3 to 4 days

50000 to 75000 20 10 10 26

4 to 5 days

75000 to 150000 26 14 16 44 180 seconds

6 to 8 days

150000 to 250000

32

20

26

56

240 seconds

10 to 14 days

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 KA 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 200 sites.

In addition to the recommended Postgres configuration in EMS installation with standalone remote database without Docker, configure the following:

  • max_connections = 9999

  • checkpoint_timeout = '2min'

Number of 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)

50

Up to 100000

24

18

26

64

180 seconds

200

Up to 20000

10

12

24

48

120 seconds

For performance issues regarding multitenancy-enabled cases, see Known issues.

Hardware configuration when EMS and Postgres run on different machines with no FortiGate connected

Hardware configuration when EMS and Postgres 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:

Number of managed endpoints

EMS server machine

Postgres server machine

Suggested keep alive (KA) interval

Deployment duration

Number of virtual CPUs Memory (RAM) (in GB)

Number of virtual CPUs

Memory (RAM) (in GB)

10000 to 20000 8 6 4 16 120 seconds

1 to 2 days

20000 to 50000 16 8 6 22

3 to 4 days

50000 to 75000 20 10 10 26

4 to 5 days

75000 to 150000 26 14 16 44 180 seconds

6 to 8 days

150000 to 250000

32

20

26

56

240 seconds

10 to 14 days

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 KA 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 200 sites.

In addition to the recommended Postgres configuration in EMS installation with standalone remote database without Docker, configure the following:

  • max_connections = 9999

  • checkpoint_timeout = '2min'

Number of 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)

50

Up to 100000

24

18

26

64

180 seconds

200

Up to 20000

10

12

24

48

120 seconds

For performance issues regarding multitenancy-enabled cases, see Known issues.