On Tuesday 27 January 2009 20:03, Dennis Nezic wrote: > On Tue, 27 Jan 2009 12:44:59 -0500, Dennis Nezic wrote: > > On Wed, 21 Jan 2009 17:28:47 +0000, Matthew Toseland wrote: > > > Give it more memory. If you can't give it more memory, throw the box > > > out the window and buy a new one. If you can't do that wait for the > > > db4o branch. > > > > Or, more likely, throw freenet out the window :|. > > > > > Seriously, EVERY time I have investigated these sorts of issues the > > > answer has been either that it is showing constant Full GC's because > > > it has slightly too little memory, or that there is external CPU > > > load. Are you absolutely completely totally > > > 100000000000000000000000000% sure that that is not the problem? > > > AFAICS there are two posters here, and just because one of them is > > > sure that the problem isn't memory doesn't necessarily mean that the > > > other one's problems are not due to memory?? > > > > My node crashed/restarted again due to MessageCore/PacketSender > > freezing for 3 minutes. The problem appears to be with cpu usage, > > since my memory usage is basically plateauing when the crash occurs, > > though I suppose the two factors may not be necessarily entirely > > unrelated. My cpu load (ie. as reported by uptime) would sometimes > > rise pretty dramatically, with a 15-min load number hovering between > > 3 and 4, which brings my system to a crawl, and I guess this > > eventually "freezes" some threads in freenet, and then triggers the > > shutdown. > > Restarting the node "fixes" the cpu-load problem, even though the node > is doing exactly the same stuff as before, at least from the user's > perspective. So, clearly, the problem is not just "slow and obsolete" > hardware as you suggest, but something else internal to the code, that > grows out of control over time--over the course of dozens of hours.
I.e. memory usage. QED! Memory usage was plateauing = memory usage was constantly at the (low) maximum, and it was using 100% CPU in a vain attempt to reclaim the last byte of memory. This is the most likely explanation by far: Can you categorically rule it out via checking freenet.loggc? You did add the wrapper.conf line I mentioned?: wrapper.java.additional.3=-Xloggc:freenet.loggc If it is a memory problem, db4o will probably solve it, however the db4o branch does do somewhat more disk access, which might conceivably be a problem on very old hardware. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 827 bytes Desc: not available URL: <https://emu.freenetproject.org/pipermail/support/attachments/20090127/73205a8d/attachment.pgp>
