1.1.4 Recommended HW

Virtual Machine Distribution

The count of the connected devices affects 2N® Access Commander in variable ways. Therefore, set the size of hardware elements for the server accordingly.

The table below indicates the recommended minimum count of CPU cores and RAM sizes for different counts of devices and users managed by 2N® Access Commander.

Count of connected devicesCount of users*Count of CPU coresAssigned RAM size
1 00010 00022 GB
2 000100 00024 GB
2 000200 00048 GB
7 000200 000416 GB

*We recommend group sizes no bigger than 1 500 users. Where area restrictions like anti pass-back or occupancy management are used with many users, the application might slow down.

Caution

  • We recommend 2N® Access Commander be connected to the devices 24/7. If 2N® Access Commander becomes disconnected from your devices, they will store an event log autonomously and, upon reconnection, synchronize the offline log data back to 2N® Access Commander. While this is happening, the application continues to run, but if there are many devices, this can take a long time.


2N® Access Commander Box

Count of connected devices 2.0Number of users 2.0
Number of users per group*

2 000

100 000

1 500

*We recommend group sizes no bigger than 1,500 users. Where area restrictions like anti pass-back or occupancy management are used with many users, the application might slow down.

Caution

  •  We recommend 2N® Access Commander be connected to the devices 24/7. If 2N® Access Commander becomes disconnected from your devices, they will store an event log autonomously and, upon reconnection, synchronize the offline log data back to 2N® Access Commander. While this is happening, the application continues to run, but if there are many devices, this can take a long time.