mirror of
https://github.com/rclone/rclone.git
synced 2024-11-07 17:14:44 +01:00
docs: add FAQ entry about rclone using too much memory
See: #2200 #1391 3196
This commit is contained in:
parent
4d195d5a52
commit
64fb4effa7
@ -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
|
||||
not to use up too much memory. You can change this default with the
|
||||
[--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.
|
||||
|
Loading…
Reference in New Issue
Block a user