For a while, for a long while actually, freenet builds have been working without pegging my cpu meters at 100%... for whatever reason, build 535 likes doing absolutely absurd things to my load average. I can have no activity for minutes and suddenly BAM! up to loadaverage 12 in seconds. Whatever is going on is getting a little silly. :/
I'm running debian unstable (kernel 2.4.19) with sun's j2re1.4.1_01 and freenet 535. I am using a K6-III 400 with 320MB of ram and a 512MB store. Another thing. I noted this before, but nobody has replied about it in a while... When I set bandwidth to 10000 or use the default using BandwidthLimit in the configuration file, freenet does NOT limit itself to using 10Kb/S - it winds up using my entire upstream (15Kb/S) more than half the time for uploading data. And I was not using other programs at the time other than an IRC client, and that uses less than a kilobyte per second. I have tried other things, and found by setting this at 5000, it works. I don't know WHY it works and the 10000 setting doesn't, only that it does work at setting 5000. Finally, I tried using the independent bandwidth settings for input and output (inputBandwidthLimit and outputBandwidthLimit) - setting input to 15000 and output to 5000 again, works. Now don't forget that I'm currently running the 535 build and I've been seeing this behavior since 532, which is when I first started using freenet. I would appreciate ideas, and general discussion of these problems as they're annoying me quite a bit. :) Tim McGrath _______________________________________________ support mailing list [EMAIL PROTECTED] http://hawk.freenetproject.org/cgi-bin/mailman/listinfo/support
