Re: Ranting about JVM's default memory limits...
Mark Space wrote:
Arne Vajh?j wrote:
But:
- it is unusual compared to anything else which makes it a problem
Which makes users complain. And defeats the purpose of having an OS
with memory management if I have to manage it myself anyway. What
happens when someone installs more memory? I have to set the limit
higher on each app to take advantage of it?
No.
Xmx is virtual memory not RAM.
So you may change it when moving from 32 bit to 64 bit OS.
It does not matter if you have 256 MB or 4 GB of RAM.
- the current default is from a previous decade
My point is the whole idea of a fixed limit is, like, 3 decades old.
Hello, 1978 called, and they want their (lack of) memory management back.
You have GC and virtual memory. It can not be more managed.
I don't think limits are oldfashioned.
I guess I could live with 256m or 512m as default.
I'd like to see Sun implement some sort of adaptive algorithm that
increased the max heap in response to GC pressure, and was able to
reduce the max heap (return memory to the OS) if the GC was able to free
a larger percentage of memory in any pass.
I belive that it already does. From Xms up to Xmx.
Arne