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

ETA and bytes left for synchronization #899

Open
uok opened this issue Oct 23, 2014 · 8 comments
Open

ETA and bytes left for synchronization #899

uok opened this issue Oct 23, 2014 · 8 comments
Labels
enhancement New features or improvements of some kind, as opposed to a problem (bug)

Comments

@uok
Copy link
Contributor

uok commented Oct 23, 2014

Since current speed and bytes left are already here it would be great to use them to calculate an ETA for download/upload of each folder and also show the time left for the sync status of each device. After successful transfers this line is hidden.

Another helpful information would be to see the total remaining size (sum of all remaining transfers) of all connected folders for each device.

label: [enhancement]

@calmh calmh added the enhancement New features or improvements of some kind, as opposed to a problem (bug) label Oct 24, 2014
@calmh
Copy link
Member

calmh commented Oct 24, 2014

Yes, would be helpful.

(It's going to be somewhat tricky at best, since we don't really know how much we need to fetch until a bit later. That a 1 GB file is out of sync might not mean we need to transfer more than 128 KB.)

@matsp
Copy link

matsp commented Mar 2, 2015

From time to time I miss this feature, too. I want to add that it would be a nice feature to see the actual file upload to each device that is connected to my own client.

@calmh calmh modified the milestone: Unplanned Jan 1, 2016
@calmh calmh removed this from the Unplanned (Contributions Welcome) milestone Feb 11, 2018
uok added a commit to uok/syncthing that referenced this issue Dec 10, 2018
@marco-m
Copy link
Contributor

marco-m commented Aug 8, 2019

I would like to mention that there is a concept called "Exponentially Weighted Moving Average", that looks like exactly fit to the use case that at the beginning you don't really know "how much you need to fetch until later".

There is this Go implementation https://github.com/VividCortex/ewma that is used by, for example, by https://github.com/vbauerster/mpb and it works well.

@ebanDev
Copy link

ebanDev commented Aug 9, 2022

Any news about this issue ?

@AudriusButkevicius
Copy link
Member

No

@KraXen72
Copy link

what is preventing this to be merged?

@tomasz1986
Copy link
Contributor

tomasz1986 commented Nov 21, 2023

what is preventing this to be merged?

This is an issue. There is no pull request that would fix it yet. In other words, there is nothing to merge for now.

@KraXen72
Copy link

i see, and #5361 was frozen due to age.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New features or improvements of some kind, as opposed to a problem (bug)
Projects
None yet
Development

No branches or pull requests

8 participants