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

Wrong ETA calculation #146

Closed
prescott66 opened this issue Jul 25, 2016 · 6 comments
Closed

Wrong ETA calculation #146

prescott66 opened this issue Jul 25, 2016 · 6 comments

Comments

@prescott66
Copy link
Contributor

Today i discovered strange ETA calculation, while updating fresh installation of Manjaro.
Update size was 326MB, real download speed was only cca 200kB/s and reamining time(ETA) was 40 seconds and after a while grows up to 2 minutes....so far away from real ETA with that speed.

@philmmanjaro
Copy link
Member

ETA is dynamicly based on the given figures from libalpm if I'm not wrong. @guinux, please correct me if needed ...

@guinux
Copy link
Collaborator

guinux commented Jul 26, 2016

Download speed is calculated everytime data is received. ETA is calculated from the average download speed so it is not precise in the beginning of the download.

@prescott66
Copy link
Contributor Author

strange is, that i had constant download speed of 200kB/s and ETA remains 2 minutes during whole download...

@guinux
Copy link
Collaborator

guinux commented Jul 27, 2016

It may dues to wrong data from libalpm or a problem in ETA calculation. Let's see there are others reports.

@robert1826
Copy link

i also confirm this

@AlpacaRotorvator
Copy link

AlpacaRotorvator commented Mar 31, 2017

I've been meaning to make precise observations on this for a while now but I always forget and go to sleep while the computer does the updates. What I can say is that even after a few minutes of download pamac still gives an ETA of about 9 minutes, which is a massive underestimation, given that most updates are 700MB+ and I'm sitting on a 1Mbps connection(ie. it actually takes about one hour and a half).

Could it be that whatever algorithm is being used doesn't hold well for cases where the user's bandwidth is much smaller than the total download size?

@guinux guinux closed this as completed in c071258 Apr 15, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants