Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

High memory usage #602

Open
varuzam opened this issue Jul 4, 2020 · 2 comments
Open

High memory usage #602

varuzam opened this issue Jul 4, 2020 · 2 comments

Comments

@varuzam
Copy link

varuzam commented Jul 4, 2020

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)

duplicacy_memory_usage

@markkuit
Copy link

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.

@RubenKelevra
Copy link

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants