On November 3, 2002 04:24 pm, Oskar Sandberg wrote: > I think I have found the cause for the perfomance issues that many nodes > have been seeing since the release of 0.5. It was the result of some bad > protocol design on my part, that came to light with the combination of > Matthew's more aggressive local routing and the large number of > announcements after the release. Basically, there was nothing to stop an > announcement from restarting an infinite number of times (on requests we > loose one HTL every time we restart, but announcements need to reach a > fixed number of nodes) so many announcements were flooding nodes with > hundreds of QueryRestarted messages. > > Build 608 will stop your node from taking part in this, and it seems to > help a lot here. But other nodes will continue to flood you, so it can > only take you half way. > > The changes will probably make it a little harder for nodes to announce > themselves as long as the network is unhealthy - but there is new > announcement code in there that is very persistant so the user should > not have to worry about that.
>From my end it looks good too. Version 608 is the _first_ version since 525 that does not peg the cpu at 100%. It still seems to use more than 525 but not too the extent that it stops doing useful work - the node is processing about 800 requests per hour (about 8400 jobs). I am using the following in freenet.conf: maximumThreads=-80 maxThreads=-80 doLoadBalance=yes overloadHigh=0.65 overloadLow=0.60 I have seen both maximumThreads and maxThreads suggested on the list. Which is correct? TIA Ed Tomlinson _______________________________________________ devl mailing list devl at freenetproject.org http://hawk.freenetproject.org/cgi-bin/mailman/listinfo/devl
