You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My node was trying to sync the state with a peer that was uploading at 600 kB/s and got to 98% and then the peer stopped uploading (haven't investigated that yet). What I noticed though is that rather than download speed updating to 0 kB/s, it must be using the average over the entire timeframe, so the download speed slowly peters out (trust me, this is the technical term). Still, 5-10 minutes after the peer stopped uploading data, my node still says it's downloading at 200 kB/s.
Calculating this correctly could be a bit tricky, but even if we go with a less sophisticated approach, like updating every 5-10 seconds, it'd still be a whole lot better than what we do today.
The text was updated successfully, but these errors were encountered:
DavidBurkett
changed the title
TxHashSet download speed not accurate-
TxHashSet download speed not accurate
Jan 29, 2019
I just experienced this exact same issue 2 days ago. I think it still needs some more work. If nobody else has experienced the problem though, I'm fine with closing it.
My node was trying to sync the state with a peer that was uploading at 600 kB/s and got to 98% and then the peer stopped uploading (haven't investigated that yet). What I noticed though is that rather than download speed updating to 0 kB/s, it must be using the average over the entire timeframe, so the download speed slowly peters out (trust me, this is the technical term). Still, 5-10 minutes after the peer stopped uploading data, my node still says it's downloading at 200 kB/s.
Calculating this correctly could be a bit tricky, but even if we go with a less sophisticated approach, like updating every 5-10 seconds, it'd still be a whole lot better than what we do today.
The text was updated successfully, but these errors were encountered: