So freenet is running happily for a few days, but the load is frequently
above 20 and my server gets unusable. I want to keep doing other stuff
on it too. I'm trying to find a solution to get it in a workable state
again (or I'll shut down my node).

But I didn't find enough info about tuning my freenet that I _really_
know what I'm doing. I need to ask someone.


Having looked at some documentation, I saw 2 options in the config file
I could use: maximumThreads and maxNodeConnections. Right or wrong?

Setting maxNodeConnetions is preferred, putting a hard limit on the
number of threads is ugly (or uglier). Right or wrong?

Well, I decreased maxNodeConnections from 30 to 8, to see what it would
do, expecting the number of threads to go down too... But what happens?
The NodeInformationServlet gives me:- the number of 'Open Connections'
is between 16 and 32, usually somewhere at 24. Why? I was expecting this
to be 8. Does maxNodeConnections not have anything to do with the number
of open connections?- in the 'Load Stats': usually 8 entries. (At the
moment it's 9.) Are those the 8 connections, then?- The Thread factory
tells me that at this moment there are 45 active threads and 18
available ones. Uhm... this is kind of much, I think... And I was kind
of hoping to get that down with the maxNodeConnections setting, but that
does not seem to be the case...

Should I just set maximumThreads to 30 or something?
Or is there another better option, to keep my node from going wild?



Misc info:
my node, with datastore of about 2GB, runs on a Sun Netra X1 (128MB RAM)
under Linux (Debian Woody). It runs with Blackdown JVM 1.3.1 (which
seems the only usable choice for linux/sparc. I tried the Kaffe .deb
-1.0.6-7+.cvs20020411- but Kaffe often just quits without notice). I'm
running build 494 (which is what is packaged for Debian unstable; I'm
lazy when I can get away with it).


--Roderik.

_______________________________________________
support mailing list
[EMAIL PROTECTED]
http://hawk.freenetproject.org/cgi-bin/mailman/listinfo/support

Reply via email to