Okay, this one took me 20 minutes to catch it happening - my node is rejecting the majority of query requests. And it works like this:
I accept every request for a 'little while' (1 to 2 minutes). Then I reject every request (for 5 to 20 minutes) until it is time to accept them all again. And the cycle repeats. I noticed a pattern like this in localQueryTraffic by minute :
10/26/03 9:24:00 PM EST 96 0 0.0 10/26/03 9:25:00 PM EST 132 0 0.0 10/26/03 9:26:00 PM EST 189 26 0.13756613756613756 10/26/03 9:27:00 PM EST 595 463 0.7781512605042017 10/26/03 9:28:00 PM EST 531 0 0.0 10/26/03 9:29:00 PM EST 323 0 0.0 10/26/03 9:30:00 PM EST 556 0 0.0 10/26/03 9:31:00 PM EST 438 0 0.0 10/26/03 9:32:00 PM EST 401 216 0.5386533665835411 10/26/03 9:33:00 PM EST 710 472 0.6647887323943662 10/26/03 9:34:00 PM EST 367 0 0.0 10/26/03 9:35:00 PM EST 250 0 0.0 10/26/03 9:36:00 PM EST 123 0 0.0 10/26/03 9:37:00 PM EST 308 0 0.0
the ratio is usually 0. So, I wanted to know, if during the active periods, there were ANY rejects. The way I determined that there were NOT, was by repeatedly clicking on Network Load .
The fourth bullet (Current proportion of requests being accepted: 0.000) sits at zero until the surge happens. Then it climbs to 1.0, and falls back to 0 again.
This is not necessarily a problem in-and-of-itself, as I AM accepting and processing some percentage of the requests. But I suspect most people would feel more comfortable if this behavior were smoothed out. I'm guessing that my outbound (forwarded) queries are surging towards my peers as well, which makes their scheduling job a -little- harder. I don't query them for 7 minutes, then "wham!"
I also notice that the number of incoming requests fluctuates in accordance with this cycle - probably the "back off" mechanism is working. Most of my peers are now 6281.
Kudos to Toad for taking his foot out of our mouths :)
_______________________________________________ Devl mailing list [EMAIL PROTECTED] http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/devl
