I have two recommendations:
1. When freenet installs, it should check the total memory available on the computer and recommend an appropriate setting for memory allocation (for a 512MB machine, I guess it should be 256MB ram). (For that matter, I guess it should also recommend a larger data store size if the user clearly has the space.)
2. Somehow, someway, someone should make it so that freenet will continue to operate no matter what amount of memory is made available to it. I have no idea what that entails.
-Martin
Brandon Low wrote:
sounds great! Strangely (very strangely) my node on 6211 hasn't started leaking memory yet, and it has been up for 7 hours... wonder if something automagically fixed that issue or something...
Anywho, if we can resolve the memory leak issue and have code that works for > 24 hour uptime then it is time to give it some more testing and
make this stable, cuz stable still CurusBugs (IRC name for opens lots of connections to one node for no good reason)
--Brandon
On Sun, 09/28/03 at 14:17:51 -0700, Martin Stone Davis wrote:
Okay, I'll change back to maxRequestsPerInterval=300, re-activate bwlimiting, and upgrade to version 6211. My machine has 512MB of RAM, so I will set JavaMem=256.
-Martin
_______________________________________________ Devl mailing list [EMAIL PROTECTED] http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/devl
