Resilio Connect Agent can work on NAS devices as well as low-profile Linux devices. There are some peculiarities an administrator should be aware of when planning to run Resilio Agent on the above mentioned devices.
- Memory consumption
Resilio Agent consumes on average 1.5Kb of memory per syncing file and each subfolder level in its path. Adding folders with a large number of files may cause your device to run out of physical memory and work extremely slowly due to swapping data to HDD/flash storage.
- CPU consumption
Resilio keeps all folders you add to it up-to-date and consumes CPU to keep track of all changes made in a folder, as well as sends it to other peers over network. The actual CPU consumption depends on the amount of top-level folders connected as well as the number of peers syncing. While exact amount of folders and peers served depends on CPU power, as a rule of thumb, it is advised not to exceed 8-10 folders and 50 peers in total for Raspberry PI-class devices.
- File change notifications
Some devices may not support file change notifications so Resilio Agent will notice changes only during rescan (10-minute period by default).
- Accessing files over Samba
If your NAS is serving files over Samba, it is not advised to access these files directly from NAS itself by the Agent. Samba daemons do excessive caching and may lead to Resilio delivering only partially changed files. In this case ensure Agent accesses files over SMB or any other network access protocol provided by your NAS.
- HDD power-saving mode
By default, Resilio re-checks all files every 10 minutes, with any changes made on other peers delivered as soon as detected. This will prevent your HDD on NAS from entering power-saving mode.
Please check supported and non-supported NAS vendors here.