• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Jeanne Boyarsky
  • Liutauras Vilda
  • Campbell Ritchie
  • Tim Cooke
  • Bear Bibeault
Sheriffs:
  • Paul Clapham
  • Junilu Lacar
  • Knute Snortum
Saloon Keepers:
  • Ron McLeod
  • Ganesh Patekar
  • Tim Moores
  • Pete Letkeman
  • Stephan van Hulst
Bartenders:
  • Carey Brown
  • Tim Holloway
  • Joe Ess

Runtime methods  RSS feed

 
Ranch Hand
Posts: 79
Android Eclipse IDE Firefox Browser
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi,

Runtime class provides api methods like
1)maxMemory()
2)totalMemory() and
3)freeMemory()

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 ?


Following is the code i wrote to check that.





Cheers,
Adithya.
 
Saloon Keeper
Posts: 9136
172
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
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.
 
author and iconoclast
Sheriff
Posts: 24220
40
Chrome Eclipse IDE Mac OS X
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Stephan is correct. freeMemory() is the amount that could be allocated right now without running the garbage collector.
 
It is sorta covered in the JavaRanch Style Guide.
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!