Navigation Menu

Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Transfer rate and time remaining estimate inaccurate on resumed transfers #7815

Closed
cyberduck opened this issue Feb 26, 2014 · 2 comments
Closed
Assignees
Milestone

Comments

@cyberduck
Copy link
Collaborator

b234361 created the issue

When resuming downloads, the transfer rate (and accordingly, the remaining time estimate) is calculated incorrectly. For example:

Assume 10MB file.

5MB was previously downloaded.

DL is resumed.

At first, the tx rate is astronomically high and the estimated remaining time shows just a few seconds. It looks like the rate/time calculation is thinking that the first 5MB were downloaded instantaneously.

Suppose it takes 1 minute to DL the next 1MB. Now perhaps the rate would show 102.4KB/s (i.e. 6MB in 1 minute) and estimate less than 1 minute left (to DL the remaining 4MB) when in fact the rate has been 17KB/s (1MB in 1 minute) and it should be 4 minutes remaining.

In other words, I think the calculation is taking into account the previously-downloaded portion, which throws things off. It would be much more helpful if only the size remaining of the file since "resume" were taken into account - then we could have more accurate time (and transfer rate) estimates.

@cyberduck
Copy link
Collaborator Author

9c870e6 commented

I can confirm this is still an issue as of build 14391

@cyberduck
Copy link
Collaborator Author

@dkocher commented

In a5539f4.

@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants