本帖最后由 ninqq 于 2020-3-19 11:37 编辑
机翻的看不懂
只看懂放到内存里
这几条具体不是很清楚
- It will use fewer transactions (important if you pay for them)
- It will use more memory. Rclone has to load the whole listing into memory.
- It may be faster because it uses fewer transactions
- It may be slower because it can’t be parallelized
- rclone should always give identical results with and without --fast-list.
复制代码
完整的
- --fast-list
- When doing anything which involves a directory listing (eg sync, copy, ls - in fact nearly every command), rclone normally lists a directory and processes it before using more directory lists to process any subdirectories. This can be parallelised and works very quickly using the least amount of memory.
- However, some remotes have a way of listing all files beneath a directory in one (or a small number) of transactions. These tend to be the bucket based remotes (eg S3, B2, GCS, Swift, Hubic).
- If you use the --fast-list flag then rclone will use this method for listing directories. This will have the following consequences for the listing:
- It will use fewer transactions (important if you pay for them)
- It will use more memory. Rclone has to load the whole listing into memory.
- It may be faster because it uses fewer transactions
- It may be slower because it can’t be parallelized
- rclone should always give identical results with and without --fast-list.
- If you pay for transactions and can fit your entire sync listing into memory then --fast-list is recommended. If you have a very big sync to do then don’t use --fast-list otherwise you will run out of memory.
- If you use --fast-list on a remote which doesn’t support it, then rclone will just ignore it.
- --timeout=TIME
复制代码 |