When planning for a deployment of NXPowerLite for File Servers please consider the following:
NXPowerLite uses a temporary folder on the machine on which it is installed to make a copy of each file and do its processing. The path to this temporary folder is determined by the TMP environment variable for the user account used by the NXPowerLite File Server service. We recommend ensuring that the disk that NXPowerLite is using is as fast as possible to avoid server slowdown. It is possible to configure the path of the TEMP folder by following the steps described in Changing the NXPowerLite for File Servers working directory. For example, setting NXPowerLite to use a SSD for TEMP directory would significantly increase performance.
CPU / RAM
CPU/RAM resources will vary according to the number of optimizers NXPowerLite is configured to use. By default NXPowerLite is configured to use 2 optimizers, which means 2 files from the scanned list, can be processed in parallel. The more optimizers that are used the more CPU & RAM resources are used. To change the number of optimizers from the default value of 2 please follow the steps outlined in How do I configure the number of optimizers to run concurrently?
If resources are scarce or heavily contested then you may want to consider installing NXPowerLite on a separate machine or VM from the file server. The software can be installed on any Windows machine as long as it can access the data that you want to reduce.
Remote deployment / Network bandwidth
If NXPowerLite is installed on a system where the data to reduce is not stored locally, please be aware that there will an increase in network traffic. Before processing a file, NXPowerLite copies each file to the machine on which it is installed. After processing, it will overwrite the original. This increases the network traffic and means the performance of the software may be limited by the available network bandwidth.
In our testing with v7.1.4 on a typical dataset, NXPowerLite will compress around 1TB of data in a 24hr period. (v6.x.x processed around 240GB in a 24hr period). The testing was performed using a machine with the following specifications:
|OS||Windows Server 2016|
|CPU||4-core i5 (8 virtual cores)|
|No. of optimizers||4|
|TEMP directory location||5400RPM HDD|
Processing time reduced by 50% by moving the location of the %TEMP% and %ProgramData% onto an SSD. ( For more details see Changing the NXPowerLite for File Servers working directory)
For large datasets, we recommend using multiple installations of NXPowerLite all configured to process discrete subsets of the entire data. This means the processing will be performed in parallel, bringing the time for completion down considerably.