Allocating resources for the Portal
Adapt the configuration of the Portal to your available hardware resources in order to maximize their utilization and optimize performance. To that end, edit the configuration file startup.properties in the Portal and set the appropriate memory values depending on your hardware resources and size of your installation.
Starting from V6.24, Nexthink runs a single-JVM on all setups (previous SMALL mode, which is implicit now). Adapt the amount of reserved memory to the size of your setup, according to the table below. The Total memory size corresponds to the actual memory installed, according to the specified minimum hardware requirements for the Portal appliance. If you are using a single appliance for both the Engine and the Portal, divide the memory installed by two (hardware requirements for a single appliance) to get an estimation of the Total memory for the Portal:
Ask Nexthink Support for setups with more than 150k devices.
To edit the configuration file of the Portal and set the values that fit your hardware:
Log in to the CLI of the Portal appliance.
Stop the Portal:
sudo systemctl stop nxportal
Make a copy of the sample configuration file to use it as the current configuration file:
sudo -u nxportal cp \
Edit the configuration file with the appropriate values from the table above:
sudo vi /var/nexthink/portal/conf/startup.properties
Restart the Portal:
sudo systemctl start nxportal
For example, in an installation with 45 000 devices, look up in the table above and find that, for a maximum of 50k devices, you must allocate 16 GB of memory.
In that case, change the values of those parameters in the startup.properties configuration file of the Portal. The file should look like this:
For large installations, please contact Nexthink for instructions on how to properly allocate resources for the Portal. You may also need to increase the number of connections to the Portal database.