alexvanin/rclone
1
0
Fork 0
forked from TrueCloudLab/rclone
Code Pull requests Activity

docs: add FAQ entry about rclone using too much memory

Browse source 
See: #2200 #1391 3196
This commit is contained in:
Nick Craig-Wood 2019-06-12 11:08:19 +01:00
parent 4d195d5a52
commit 64fb4effa7
1 changed files with 16 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

16
docs/content/faq.md
View file

@ -195,3 +195,19 @@ It is likely you have more than 10,000 files that need to be
synced. By default rclone only gets 10,000 files ahead in a sync so as synced. By default rclone only gets 10,000 files ahead in a sync so as
not to use up too much memory. You can change this default with the not to use up too much memory. You can change this default with the
[--max-backlog](/docs/#max-backlog-n) flag. [--max-backlog](/docs/#max-backlog-n) flag.
### Rclone is using too much memory or appears to have a memory leak
Rclone is written in Go which uses a garbage collector. The default
settings for the garbage collector mean that it runs when the heap
size has doubled.
However it is possible to tune the garbage collector to use less
memory by [setting GOGC](https://dave.cheney.net/tag/gogc) to a lower
value, say `export GOGC=20`. This will make the garbage collector
work harder, reducing memory size at the expense of CPU usage.
The most common cause of rclone using lots of memory is a single
directory with thousands or millions of files in. Rclone has to load
this entirely into memory as rclone objects. Each Rclone object takes
0.5k-1k of memory.