Open varuzam opened 4 years ago
duplicacy holds 2GB RAM for me with ~4800 files totaling short of 2TB, and it can only get worse as the numbers on file grow. I have no choice but stay away from it as it makes backing up a liability.
Strange, not really an issue here, consumes 192 MB:
USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
rubenk 694016 86.1 1.2 1826468 204832 pts/2 Sl+ 05:03 43:52 duplicacy backup -storage vidar -threads 4
Maybe an issue with the go runtime in the past? As it is doing the garbage collection for Duplicacy it can have an impact
I always used borgbackup so far. I tried duplicacy with a hope it uses RAM more efficiently. In my case ( backing up of ~ 780000 files) duplicacy consumed 3 times more memory (1.1GB) than borgbackup(350MB)