On Thu, Oct 09, 2003 at 01:31:04AM +0100, Jonathan Howard wrote: > Should the code be changed so highly overloaded nodes send DNFs when the > keys are in the Failure Table.
Changed? It already does! Unless we are rejecting connections, we accept queries we know will fail fast or succeed fast. > > -------------- > How about a cooling off period after receiving QueryRejected before > sending anything else to the node. We used to have this in CPAlgoRT. It didn't work and was in any case alchemy/voodoo. NGRouting will make rational decisions based on the likelihood of a QueryRejected. > > -------------- > Attached is a changed version of StandardNodeEstimator.estimate() using > t/pSuccess. > I can't judge fairly. I do see my routing table now has some nodes with > lower 'Search died probability' getting the most successes. I don't really see what the point is with the rest. > > -------------- > Looking in my routing table the node is 6215, so maybe this has been > fixed. (If your lucky) > I saw this message received (one odd out of thousands) > The odd bit appears all over as part of 'Storable.Public-key.p=' > The matching UniqueID had been Accepted. > Other standard traffic to the node was in between. Some but not all > overloaded. > Sorry, (if) any output to freenets log is gone. -- 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
