Toad wrote:
After investigating some strange estimates, it appears that tSearchFailed can take some absurdly high values, because of the different things it is used for: QueryRejected's, timeouts in place of a QueryRejected, timeouts after Accepted, timeouts after QueryRestarted's.
Options: 1. Add separate estimators for each option. If it works, it may partially explain routing breakage, and may be less alchemical than exponential backoff. 2. Remove pSearchFailed from the estimators altogether. Leave load balancing entirely to exponential backoff.
Anyone in favour of option 1) ? :)
Me.
Me too. While I may feel like a lamb lost in the woods, when facing the deluge of variables on the diagnostics page, I think this will allow even more human examination of the routing process, as a system. One that still needs debugging !
Ken
_______________________________________________ Devl mailing list [EMAIL PROTECTED] http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/devl
