Unfortunately this didn't help. The node is behaving erratically - at times there is hardly any load, CPU 5-10 % loaded. At other times there the log is filled with messages of receiving packets twice and the CPU goes to 100%. Also ping times are increased - also the minimum ones.
But have to move this to support I guess. The minimum ping time doesn't seem to be any different from the average. -- Malkus Lindroos Malkus Lindroos wrote: > And finally, you were right of course. The problem wasn't the rate > limiting code, but a configuration problem on my node. The node connects > by default to all interfaces (0.0.0.0), which apparently caused problems > - the log was filled with messages of receiving packets twice. This > caused heavy load occasionally to the node. Limiting to only one > interface fixed the problem. > > The node is currently running using minpingtime as well, just to test > its effects. There still are nodes with very high ping times in my lists > that push the average pings times higher than they should be, but it is > not really a problem (yet). >
