> >>The real question is: how much of your outgoing bw > >>is used up by QR:s, how much is used by routing requests, and how much > >>is used up by "real" data. I wish I knew how to tell this. > > > > > > Check outputBytes* in the diagnostics. Low is actual data (trailers) and > > the others mostly are things like DataRequests and QRs and other things > > > > Lemme make sure I understand this. > > From servlet/nodestatus/diagnostics/outputBytesLow/minute: > >Events Value Change Mean Total Value Mean Time Between Events > >2072 578015 1.3937197026238224E8 29.047779922779924 > > From servlet/nodestatus/diagnostics/outputBytes/minute: > >Events Value Change Mean Total Value Mean Time Between Events > >386 649802 1.6627010963104272E8 155.36010362694302 > > That means that in one minute, I sent out 578015 "real" data bytes and > 649802 total? If so, my node is doing very well sending data, despite > the large number of QR:s!
Exactly the same conclusion that I seem to come to whenever I check my node:s status :) And... some of those outputBytes that isn't prio 'Low' might be data too.. I think it works something like: when a trailer has waited long enough it will be escalated to a higher prio.. /N _______________________________________________ Devl mailing list [EMAIL PROTECTED] http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/devl
