S <freenet at ...> writes: > I would venture to say that increasing VM is more likely to increase > disk access, not decrease it. -Xmx does seem to be what you want, > though; it will set a ceiling on the amount of RAM that Java will > allocate. > > Try disabling Virtual Memory in Windows altogether, and see if that > helps any with the disk thrashing. You should be able to run Windows > plus Freenet reasonably well in 640 megs, especially if you kill off any > tray utilities and unnecessary services. Check the task manager to see > how much RAM Windows wants for itself, then use -Xmx (or FLaunch.ini) to > give Java most of whatever's left. > > s
In my haste to post, I said "VM to 192..." I meant JavaMem. Looking at the task manager, I'm not seeing any paging per se, so I don't think that is it. It seems to be a periodic task that freenet itself is performing. It might go away if I dropped a drive in that had a decent cache. This is a 5 year old 30GB maxtor drive, and I doubt it has much of a cache on the drive itself. I think I really need to dig up another box with a wee bit more modern CPU and drive. OK, I'm really beginning to hate all the limitations on the web version of the gmane support page. Time to get on the list. Pathetic thing can't even linewrap. Squirrel
