extern/rclone
1
0
Fork 0
mirror of https://github.com/rclone/rclone.git synced 2025-02-17 19:11:33 +01:00
Code Issues Packages Projects Releases Wiki Activity

Updated Documenting rclone Optimizations discussion page (markdown)

calisro 2017-07-06 10:26:19 -04:00
parent 2b276c1504
commit a04b418290
1 changed files with 12 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
Documenting-rclone-Optimizations---discussion-page.md

@ -1,2 +1,14 @@
# Ideas for optimizations which should be documented
## When to use/not use --no-traverse:
Let's say you have a destination with 6 files {a,b,c,d,e,f}.
If you are copying {a} to the destination then without no-traverse, rclone will load in the definitions for all the files {a,b,c,d,e,f} before discovering whether {a} needs to be uploaded. If you use --no-traverse rclone will just check {a} on the remote.
So why wouldn't you use --no-traverse all the time?
If you are copying {a,b,c,d,e,f} to the destination, then rclone will check each file individually. This will take at least 6 transactions, whereas likely you could have got the listing for all the objects done in 1 listing.
So there are tradeoffs! The new sync method implemented in 1.36 makes --no-traverse less useful than it used to be, but it can still come in handy, especially if you are moving or copying files into a deep hierarchy.