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

time estimates shows wrong values #2328

Closed
moscicki opened this issue Oct 18, 2014 · 8 comments
Closed

time estimates shows wrong values #2328

moscicki opened this issue Oct 18, 2014 · 8 comments
Assignees
Labels
ReadyToTest QA, please validate the fix/enhancement sev4-low type:bug

Comments

@moscicki
Copy link
Contributor

Time estimates are very confusing in 1.7. See attached screenshot.

Several issues:

Estimated total time is smaller then estimated download of the current file. I guess it has to do with the parallel download.

Also the time estimate for the current file refreshes very quickly (and changes all the time=>completely unreliable) while the total time refreshes every second and seems more stable and reliable.

Also, Occasionally I saw some time estimates like 1y10month to complete (for very large directories, ~100K files). That was clearly wrong because in reality it took 1 hour or so.

image

After a while both time estimates got closer (still total<current file download time):

image

@enoch85
Copy link
Member

enoch85 commented Oct 18, 2014

CC @dark-eye

@guruz guruz added this to the 1.7.1 milestone Oct 19, 2014
@ghost
Copy link

ghost commented Dec 11, 2014

Related : #2521

@enoch85
Copy link
Member

enoch85 commented Dec 11, 2014

Related #2400

@dragotin dragotin changed the title time estimates: very confusing time estimates shows wrong values Dec 12, 2014
@dragotin dragotin modified the milestones: 1.8 - UI Enhancements, 1.7.1 Dec 12, 2014
@dark-eye
Copy link
Contributor

(Sorry for the late reaspone didn't see this issue until now ).

I made the current file more responsive on purpose to show the actual download/upload ratios and the total is more of an average over time (which should be the correct time)
I can make them equal and prevent a visible estimate (with "estimating..." text instead) on both total and current file until they'll have a reliable estimate but that will create a different bug that short files/updates will have no estimate at all (part of the reason i made the current file more responsive)

I`ll work on it once i get home

ckamm added a commit that referenced this issue Jan 30, 2015
The current algorithm doesn't care much, but resetting progress
to 0 just before completing a job is confusing anyway.
@ckamm ckamm assigned ckamm and unassigned dark-eye Jan 30, 2015
@ckamm
Copy link
Contributor

ckamm commented Jan 30, 2015

Initial work for this has gone into the 'timing' branch.

@dark-eye
Copy link
Contributor

I found a bug in my implementation that if the user connection was slow for a long time and then it sped back up it will show a very long estimate, for example:

if a user transfer a 100Mb file and it internet slowed to 8kbs for an hour and then sped up back again to 2Mbs it will show more then an hour up until 75% of the file was transferred.

the reason for that it look at the past and see that it took 1 hour to transfer 35Mb so it should take 2.5 more to transfer the rest (even though with 2mb/s it should actually take less then a minutes...

ckamm added a commit to ckamm/owncloud-client that referenced this issue Mar 27, 2015
The current algorithm doesn't care much, but resetting progress
to 0 just before completing a job is confusing anyway.
ckamm added a commit to ckamm/owncloud-client that referenced this issue Mar 27, 2015
ckamm added a commit to ckamm/owncloud-client that referenced this issue Mar 27, 2015
ckamm added a commit that referenced this issue Apr 22, 2015
The current algorithm doesn't care much, but resetting progress
to 0 just before completing a job is confusing anyway.
@ckamm
Copy link
Contributor

ckamm commented Apr 22, 2015

Merged into master branch. There's a lot of improvements that could still be done to the time estimation code...

@ckamm ckamm added the ReadyToTest QA, please validate the fix/enhancement label Apr 22, 2015
@Dianafg76
Copy link

I tested the bug, and the time estimates shows wrong values. So I close the bug
Desktop v1.8.2 (build 2362)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ReadyToTest QA, please validate the fix/enhancement sev4-low type:bug
Projects
None yet
Development

No branches or pull requests

7 participants