rclone/rclone

When max transfers set, limit sync backlog to the max-transfer amount

Open

#3,974 opened on 2020年2月17日

GitHub で見る
 (4 comments) (0 reactions) (0 assignees)Go (57,185 stars) (5,090 forks)batch import
bandwidthchange detectionenhancementhelp wanted

説明

What is your current rclone version (output from rclone version)?

1.51.0

What problem are you are trying to solve?

When using sync with --max-transfer, it would be nice to automatically limit the sync backlog to stop after reaching the limit set by --max-transfer.

How do you think rclone should be changed to solve that?

There is no point in continuing to build the backlog beyond that point, so it should stop getting more files to upload once it gathered enough to fulfill the max-transfer amount.

コントリビューターガイド

技術スタック
go
領域
clicloud
Issue 種別
feature
難度新しい貢献者にとっての実装難度です。1 は非常に小さな変更、5 は専門的な作業です。
3
推定時間経験ある貢献者が調査、実装、テスト、pull request 準備にかけるおおよその時間範囲です。
1-2 days
活動状況Issue が今どれだけ取り組みやすいかを示します。新しい、活発、古い、ブロック中、またはメンテナー入力待ちなどです。
stale
明確さ期待される変更、受け入れ条件、次の手順がどれだけ明確かを示します。
clear
前提条件
Familiarity with rclone's sync logicGo programming basics
初心者向け度初回貢献者にどれだけ取り組みやすいかを 1-100 で推定したスコアです。
25
調査方針
The issue requests that when max transfer is set, the sync backlog should be limited to the max transfer amount. To implement this, one should examine the rclone sync code, likely in the fs/sync directory, to understand how the backlog is built and how to stop gathering more files once the limit is reached. The issue has no recent activity, so it may require rebasing on the current codebase.