On Fri, 28 Nov 2003 08:14:23 -0500, Andrew Rodland wrote: > >> BTW. Wasn't the whole point of NGRouting to ease the development by >> allowing one to improve the algorithm simply by comparing the estimated >> and observed routing times - the closer they are, the better ? Wouldn't it >> make sense to perform such an observation, possibly by adding a new column >> to the Routing Table Status, EstimateError, which would show the average >> estimate error for this node, as well as the maximum and minumum values ? >> And possibly the mean values for per-key average errors of all queries ? >> This might show whether the current estimate formula is working or not, >> and, as a consequence, if the current problems are caused by it or >> something else. >> >> If such a stat already exist, then I apologize for bothering you, but I >> wasn't able to find anything like this from the Node Status Info or >> subpages. > > (absD|d)iffSearchSuccessTime and (absD|d)iffTransferRate in diagnostics.
Thank you. Apparently, the estimated search time is constantly too low, as is the estimated transfer rate. _______________________________________________ Devl mailing list [EMAIL PROTECTED] http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/devl
