On Friday 08 May 2009 17:40:58 Juiceman wrote: > >> Weird. node.db4o was an insane 375 MB. I deleted it and and added a > >> bunch of downloads. Now it is less than 10 MB. That definitely > >> helped some with the disk thrashing. > >> > >> I think I found the main problem, and I'm embarrassed to say > >> apparantly I had xmlspider plugin running and writing GB+ files to the > >> same disk the node resides on. I turned this off and the disk usage > >> became manageable. > >> > >> I also upgraded my HDD from an older 2 MB cache model to one with 16 > >> MB and now Freenet is zipping along nicely. > >> > >> I did see some errors in the log so I am sending it to Toad for review. > >> > >> P.S. I would recommend not installing the xmlspider by default on installs. > >> > >> Victor - might this be your issue as well? > > > > ROFL. So that just leaves victor... > > Is it normal that node.db4o never shrinks? I have completed all the > downloads I had running and removed them from the page, yet node.db4o > doesn't get smaller. I have rebooted the node also. This IMHO is bad > because it will eventually kill performance with disk access...
Yes, the only way to ensure it shrinks is to defrag it. This is on the todo list, but it does not seem urgent to me. Is it really a huge, monstrous, evil, all-consuming problem more urgent than the 500 other things we have to deal with?
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Support mailing list Support@freenetproject.org http://news.gmane.org/gmane.network.freenet.support Unsubscribe at http://emu.freenetproject.org/cgi-bin/mailman/listinfo/support Or mailto:support-requ...@freenetproject.org?subject=unsubscribe
