1.1.4 Recommended HW
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 tables below include the recommended count of CPU cores and RAM sizes for different counts of devices and users managed by 2N® Access Commander.
Where 2N® Access Commander’s own application interface is used:
| Count of connected devices | Count of users | Maximum users per group | Count of CPU cores | Assigned RAM size |
|---|---|---|---|---|
| 500 | 7 000 | 1 500 | 2 | 2 GB |
* Where Anti-passback is used, the count of the users who may enter the Anti-passback area should not be higher than the maximum users per group.
Where interfacing with 2N® Access Commander via its API is used:
| Count of connected devices | Count of users | Count of CPU cores | Assigned RAM size |
|---|---|---|---|
1000 | 10 000 | 2 | 2 GB |
2000 | 100 000 | 2 | 4 GB |
2000 | 200 000 | 4 | 8 GB |
Caution
- Please be advised that we recommend 2N® Access Commander be connected to the devices 24/7. If 2N® Access Commander becomes disconnected from your devices, the devices 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 the event and access logs are updated in the background whilst the data is being processed. If there are many devices, this can take a long time.