Is it normal for a node without any bandwidth throttling with about 1 Mb of symmetric bandwidth to max out at under 16 KB/s (1/8 of the actual available bandwidth)? At first, for about an hour, the node will go and consume 100% of the available bandwidth, then it will start to overload and slow down, and very quickly reach a reasonably steady state at about 16 KB/s. This has been observed on a dual 1 GHz P3 server. Quite frequently, the node will spike it's CPU consumption to 100% (both CPUs), but most of the time it is using up at least all of one CPU.
I have deliverately switched off bandwidth throttling to see if this was the cause of the problem, and it would appear that it isn't. The number of threads and the routing time are on overload most of the time. This has been observed with unstable 6162, 6163 and 6167 on Linux, Sun's JVM 1.4.2. 6168 seems to be doing slightly better but not by much. Does anybody know where the bottleneck on this particular problem is? Increasing the number of threads from 128 to 256 only seems to make the problem worse, especially seen as after a while the cause of the overload seems to be the routing time. The node will typically continue to chug along this way until it is restarted, at which point the cycle seems to repeat, i.e. max out the bandwidth, then after an hour or so fall back down to overload speeds. Gordan _______________________________________________ Devl mailing list [EMAIL PROTECTED] http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/devl
