Menu

#16 Estimated Time Remaining is inaccurate

v1.0 (example)
open
nobody
None
5
2018-02-10
2018-02-10
newhoa
No

The Estimated Time Remaining is all over the place. I can transfer TBs of data and it will stick to around 30 minutes when in fact it's dozens of hours. Or I can transfer a few 100MB and it can say 17 Minutes remaining when it finishes in a minute or two. I'm using grsync 1.2.6 but this has happened in previous versions as I have been using it for some time and this has always been the case.

When doing a dry-run, grsync will collect how much data is being sent very quickly. Does it do the same before executing the file transfers for the full run? If so shouldn't it be able to more accurately calculate between the data total and the average transfer speed of the device?

If it would make it more accurate maybe an option for more accurate estimate time could exist where grsync would do a minute benchmark of a few file sizes and average the transfer speed.

Or maybe grsync could associate the average transfer speed with a UUID and save it in the profile data so when using the same devices or profile again it would know the transfer speed.

Anyway, just some thoughts. It's a fairly minor bug since grsync does everything else and all the important stuff so well! Thank you all so much for this great program!

Discussion


Log in to post a comment.

MongoDB Logo MongoDB