rclone / rclone/rclone

Feature request: Calculate ETA based on size of remaining files + speed for file size

Open
#6,559 7 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement stats
Dominant language
Go
Stars
59.8k
Forks
5.4k
Avg merge
2d 14h
Merged PRs (30d)
48

Description

The associated forum post URL from https://forum.rclone.org

N/A (I'm just creating this issue to get comments/suggestions before implementing it, as CONTRIBUTING.md said I should)

What is your current rclone version (output from rclone version)?
rclone v1.60.0
- os/version: darwin 12.5.1 (64 bit)
- os/kernel: 21.6.0 (arm64)
- os/type: darwin
- os/arch: arm64
- go/version: go1.19.2
- go/linking: dynamic
- go/tags: none
What problem are you are trying to solve?

When an operation (copying an either home dir) has a mix of a lot of small files as well as big files, the ETA is inaccurate, jumping from several hours to 14 weeks.

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

Having file size "brackets" (<1KB, <1MB, <100MB, <1GB, <10GB) with the current rolling average applied to each bracket (files are placed in the brackets as they're transferred, and after there's enough info, the ETA is calculated for all remaining files. This should be possible as rclone already scans for all files before starting any transferring so it should have the file sizes of each file. To keep memory usage low, just a count of files in each bracket would be kept, not assigning a bracket on a file-by-file basis.)

I'd like to try and implement this if it seems to be a good feature for rclone.

How to use GitHub
  • Please use the 👍 reaction to show that you are affected by the same issue.
  • Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
  • Subscribe to receive notifications on status change and new comments.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating rclone's transfer progress and ETA calculation in the Go code, then trace how the initial file scan and rolling transfer speed are represented. Compare the current estimate with mixed small and large files; done means the ETA uses remaining file-size groups and tests cover that scenario.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
cli, performance
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.