[Tech] Memory usage a problem?

[toad]

Anonym was having problems with datastore resizing taking forever.
Increasing the memory allocation greatly alleviated the situation:

----- toad at zceUWxlSaHLmvEMnbr4RHnVfehA ----- 2006.11.03 - 11:50:18GMT -----

Hmmm, I wonder if it would be faster if we just dropped the database while moving, and then reconstructed it afterwards?

----- Anonym ----- 2006.11.03 - 18:21:49GMT -----

OK, I did two things. I manually downloaded a new freenet-latest-.jar and freenet-ext.jar from freenetproject /alpha website. I also raised my max memory setting in wrapper conf to 256MB. I'm not sure which of those did the trick but I did the update again and this time it took one hour and completed no problem. No 100%CPU usage during the "moving" process and data read/writes were in the MB/sec or higher.

Sorry for any name calling. I was at wits end. thanks for your suggestions..oh, wait a minute, there were none :-)



sTubbY also found that increasing the maximum memory allocation helps:

----- vazee at jPTqfVl9dH3zb3AUOSeeIXG4sJ8 ----- 2006.10.25 - 20:14:01GMT -----

hi,

i very often get java errors and the node restarts, in the wrapper log it says something like 'udp socketmanager froze for 3 minutes', after that there are hundreds of lines of errors, then the node restarts and maybe runs for about 2 hours, then it happens again. strange thing is when i first installed freenet 0.7 this problem didn't occur, but after running freenet for about 3 or 4 weeks it suddenly started to produce these errors. i switched to sun jvm 1.6beta2 but it didnt get better. i tried reinstalling freenet - nothing seems to help. anyone has any idea what the problen is? i'm running windows xp prof...

thank you very much!

----- cptn_insano at _g2YxqIynCrs2bcwLGQkr+0b544 ----- 2006.11.03 - 22:29:16GMT -----

I think I've had a similar problem when the cpu is saturated by a higher priority app but there isn't much you can do except raising freenet's priority though I wouldn't recommend it.

----- sTubbY at P34k9Tn20C69pLEltGe1UFACbCI ----- 2006.11.04 - 06:09:20GMT -----

He might try raising the default memory settings in the wrapper.conf file if he can spare it.
I have found my node runs much more smoothly if you double the default memory settings.

I also run winxp and have mine set to:

wrapper.java.initmemory=128
wrapper.java.maxmemory=256

Not sure whether you need to set the min to 128, from the default of 60 I believe but I did it anyway since I was allotting 256 anyway she may as well have 128 off the bat.
But setting max to 256 smooths out the cpu hogging and spikes and less java OOM errors. I can usually run for about a week in between restarts.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://emu.freenetproject.org/pipermail/tech/attachments/20061108/739edbbd/attachment.pgp