On Sunday 07 September 2008 16:38, Peter J. wrote: > On Saturday 06 September 2008 20:46:25 Matthew Toseland wrote: > > On Saturday 06 September 2008 18:56, Peter J. wrote: > > <snip> > > > > 3. That could explain alot: > > > ????????download: aprox. 3.3 Gib > > > ????????upload ? ? : aprox. 2.4 Gib > > > > That's a fair amount too. The downloads will use a significant amount of > > RAM, the uploads will use a huge amount of RAM. You might like to try to > > db4o branch, although there's a good chance the uploads won't work ... I > > will work on uploads soon... > > > > Does increasing the memory limit help, or is it as high as you can go > > without hitting swap already? > > > > Ok, I set the maximum allocatable memory for java to 1016 MiB. I saw the > actual allocated memory rise to around 1000 Mib once then it dropped and it > is now fluctuating somewhere between 700 Mib and 850 Mib. The node is now > running for 6 hours. The computer is swapping some memory (for the first time > actually ;) ) but that doesn't really hurt the performance. > Maybe if I drop 100 Mib memory it won't use swap anymore but as I don't notice > any significant lost of performance I think I keep it this way. > > Anyway, thanks for the advise.
Let me know if this makes it stable. As regards swapping, swapping and java don't mix very well: if part of the JVM is swapped out, it will have to be paged back in to do garbage collection, which may happen every 10 seconds or so... > > Greetings -------------- 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/20080910/f447eb24/attachment.pgp>
