This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
Runtime class provides api methods like
I was under the impression that :
(1)maxMemory() is the max memory which JVM can work upon (say 128 MB)
(2)totalMemory() is the available memory with JVM (say 100MB)
(3)freeMemory() is the memory which JVM can work upon if it needs to allocate memory to objects,etc. (say 28MB).
I was guessing that
maxMemory = totalMemory + freeMemory.
but it isn't so !!
1)Can anyone explain why the above equation isn't true ?How do we figure out the relation between these (we need to have some calculation in place so that we know how much memory we are using or how much memory we will require more) ?
2)How do we decide the max memory we can allocate to the JVM ?
I'm not exactly sure, but my guess is that totalMemory() is the amount of memory that is available to the JVM right now and maxMemory is the maximum amount of memory that the JVM will request from the OS.
The JVM doesn't immediately request all the memory it can get. It will request some, use that memory (which affects freeMemory()) and when it needs more free memory, but there aren't any objects to be garbage collected, it will request more memory from the OS, adding this to totalMemory(). It will keep doing this until it hits maxMemory(), at this point it will throw an OutOfMemoryError.
Again, this is only my best guess.
The mind is a strange and wonderful thing. I'm not sure that it will ever be able to figure itself out, everything else, maybe. From the atom to the universe, everything, except itself.