Unstable 6356 is in CVS, estimators are updating. Major changes: New nodes' estimators are initialized to pessimstic defaults based normally on the worst of the routing table. We were initializing the time estimators (success search and DNF time) to a peak of twice the maximum of respectable nodes' max times, and a trough of the maximum of respectable nodes' max times. A node could become respectable (5 successful transfers - 1 if we are messed up), and still have a pretty high maximum estimate, resulting in an exponential increase in the initial estimators - degenerate pessimism, if you like. The fix is to use the maximum of the lowest times, rather than the maximum of the highest times, because the lowest times are likely to have been influenced more by the requests. We will still end up with sufficiently pessimistic estimates, hopefully. The converse applies for transfer rates - we use the minimum of the fastest transfer rate for each node.
Symptoms this was producing: the most obvious was that when you restart a node after some hours, it would wipe it's routing table (the nodes would still be there, but they'd all be reinitialized with flat estimators). Other, worse effects on routing are likely - but they only applied to new nodes. -- Matthew J Toseland - [EMAIL PROTECTED] Freenet Project Official Codemonkey - http://freenetproject.org/ ICTHUS - Nothing is impossible. Our Boss says so.
signature.asc
Description: Digital signature
_______________________________________________ Devl mailing list [EMAIL PROTECTED] http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/devl
