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.
CPU / RAM
To a lesser extent, NXPowerLite will be limited by CPU or RAM. This will depend on the size and content of each individual file, but a system with dual-core CPU and 4GB RAM would usually be more than enough.
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. It will then overwrite the original. This increases the network traffic and means the performance of the software may be limited by the available network bandwidth.
On average, NXPowerLite will compress around 100GB of data in a 24hr period. This can vary depending on infrastructure and network performance. We are focusing on improving the speed significantly for a planned release in early 2017.
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.