>> I know, but I hoped that there was some 'magic' option of JVM which
>> forbids WinXP to move ram [sic] to page file.
[quoted text clipped - 4 lines]
> OK, only the first option actually forbids Win XP to swap the JVM's
> RAM. The others can help, though.
I think there is some magic you can do - but note that it will not be
portable to other OSs.
Take a look at the KeepResident plugin for eclipse:
http://suif.stanford.edu/pub/keepresident/
This shows you how to do it.
Windows is over-zealous about paging out because it thinks its better to
keep memory for disk buffer cache than for your large (in Windows terms)
badly behaved JVM.......
Dave
Jim Garrison - 11 Jun 2007 22:21 GMT
>>> I know, but I hoped that there was some 'magic' option of JVM which
>>> forbids WinXP to move ram [sic] to page file.
[quoted text clipped - 19 lines]
>
> Dave
If you have sufficient physical memory (2GB or more) you could
just disable paging at the OS level. I routinely run my 2GB
desktop and laptop with paging turned off (paging file size == 0).
Ed Jensen - 12 Jun 2007 21:02 GMT
> If you have sufficient physical memory (2GB or more) you could
> just disable paging at the OS level. I routinely run my 2GB
> desktop and laptop with paging turned off (paging file size == 0).
I do the same thing.
Even though I never exhaust physical RAM, I've noticed that disabling
the page file on Windows results in a huge performance increase.
Linux doesn't seem to have this problem.
Jim Garrison - 13 Jun 2007 15:07 GMT
>> If you have sufficient physical memory (2GB or more) you could
>> just disable paging at the OS level. I routinely run my 2GB
[quoted text clipped - 6 lines]
>
> Linux doesn't seem to have this problem.
As someone else said, Windows is very aggressive about swapping
out application code in favor of I/O buffers, while Linux
uses a more sane approach. In linux you can actually control
the 'swappiness' of the system as a whole (but I can't remember
the parameter right now).