>> >> nodeAveragePingTime: 1592ms >> >is not normal. >> > >> >it seems that toad's new indicator pInstantReject is more revelant :) than >> >backoff. >> >> currently: >> >> bwlimitDelayTime: 4ms >> nodeAveragePingTime: 817ms >> networkSizeEstimate: 113 nodes >> nodeUptime: 45m24s >> missRoutingDistance: 0,0413 >> backedoffPercent: 18,7% >> pInstantReject: 74,9% >> >> with 7 connected and 2 backed off nodes (no disconnected ones anymore, I >> purged them) > >I don't think that purging disconnected peers will help much ... but >decreasing the averal number of peers might. > >817ms is still a high latency... I suggest you get rid of your link with the >highest ping time.
which one? the one with 3864ms, 1841ms, 1607ms, 3792ms or one the others that are alike? :D I cut them down to 4 connected nodes, let's see if that helps. Content is coming through, albeit slow, so essentially it works even with low bandwidth and high ping times! Okay, I restarted my node and it now looks like this: bwlimitDelayTime: 14ms nodeAveragePingTime: 391ms networkSizeEstimate: 24 nodes nodeUptime: 8m35s missRoutingDistance: 0,0010 backedoffPercent: 0,5% pInstantReject: 0,0% eventhough frost is now running in the background! hm *clueless* maybe the disconnected peers dragged me down? maybe my cpu was overloaded by something? dunno...
