search

AmesCornish / buttersink

Buttersink is like rsync for btrfs snapshots
GNU General Public License v3.0
193 stars 18 forks source link

Progess output reports weird results #44

Closed ceremcem closed 6 years ago

ceremcem commented 7 years ago

Here is a part of synchronization progress output of a fresh synchronization session:

0:28:01.679565: Sent 28.11 GiB of 30.58 GiB (91%) ETA: 0:02:28.066585 (144 Mbps )
0:28:02.911090: Sent 28.12 GiB of 30.58 GiB (91%) ETA: 0:02:26.903429 (144 Mbps )
0:28:04.528255: Sent 28.14 GiB of 30.58 GiB (92%) ETA: 0:02:25.773551 (144 Mbps )

It's very helpful. We have 30.58 GiB of data to send and we sent 28.14 GiB of it, which is 28.14 / 30.58 = 92%.

Now I take another snapshot (which I expect a few MiB to change) and here is its progress results: 

0:00:33.005008: Sent 880 MiB of 395.4 MiB (222%) ETA: None (224 Mbps )          
0:00:33.675362: Sent 900 MiB of 395.4 MiB (227%) ETA: None (224 Mbps )          
0:00:34.304221: Sent 920 MiB of 395.4 MiB (232%) ETA: None (225 Mbps )          
0:00:34.936035: Sent 940 MiB of 395.4 MiB (237%) ETA: None (226 Mbps )          
0:00:35.584806: Sent 960 MiB of 395.4 MiB (242%) ETA: None (226 Mbps )          
0:00:35.603220: Sent 960.5 MiB of 395.4 MiB (242%) ETA: None (226 Mbps )        
0:00:35.603273: Sent 960.5 MiB ETA: None (226 Mbps )                     

  measured size (960.5 MiB), estimated size (395.4 MiB)

How many MiB's are there to send? How many MiB's has been sent?

Obviously, it's confusing during the transfers.

Proposal

Estimated size might be left out in order to prevent confusion. It estimates mostly wrong.

ceremcem commented 7 years ago

Moreover, my laptop's wifi speed is reported as 5 Gbps: 

0:00:01.961603: Sent 1.211 GiB of 676 MiB (183%) ETA: None (5.3e+03 Mbps )      
0:00:01.993639: Sent 1.23 GiB of 676 MiB (186%) ETA: None (5.3e+03 Mbps )       
0:00:02.024546: Sent 1.25 GiB of 676 MiB (189%) ETA: None (5.3e+03 Mbps )       
0:00:02.053869: Sent 1.27 GiB of 676 MiB (192%) ETA: None (5.31e+03 Mbps )      
0:00:02.082361: Sent 1.289 GiB of 676 MiB (195%) ETA: None (5.32e+03 Mbps )     
0:00:02.113573: Sent 1.309 GiB of 676 MiB (198%) ETA: None (5.32e+03 Mbps )     
0:00:02.145109: Sent 1.328 GiB of 676 MiB (201%) ETA: None (5.32e+03 Mbps )     
0:00:02.180739: Sent 1.348 GiB of 676 MiB (204%) ETA: None (5.31e+03 Mbps )     
0:00:02.209874: Sent 1.367 GiB of 676 MiB (207%) ETA: None (5.31e+03 Mbps )     
0:00:02.238177: Sent 1.387 GiB of 676 MiB (210%) ETA: None (5.32e+03 Mbps )     
0:00:02.253126: Sent 1.399 GiB of 676 MiB (211%) ETA: None (5.33e+03 Mbps )     
0:00:02.253147: Sent 1.399 GiB ETA: None (5.33e+03 Mbps )                     

  measured size (1.399 GiB), estimated size (676 MiB)
  measured size (1.268 GiB), estimated size (1.268 GiB)
AmesCornish commented 6 years ago

Yes, estimates can be wrong by quite a bit. It's still a potentially useful option.