Why, then, on my JVM web app, when I specify -Xmx2g, do I see a Java process eating up 10g on my system? -Xmx doesn't seem to honor anything I give it - it just uses up all the memory on my server.
On Aug 12, 11:53 am, PhilDin <philb%[email protected]> wrote: > I've always wondered about this, before I encountered OOM, I just > assumed that the JVM would keep asking for memory until the underlying > OS refused to give it any more. Then, when I found the -Xmx switch, I > assumed that there was an option to specify "as much as you can get > from the OS" but again, no. > > I imagine the people working on the JVM are a little smarter than the > average bear so there's probably good, non-trivial reasons for > requiring -Xmx but I don't know what they are. Can anyone give some > pointers on this? Also, what does the .Net CLR do? Does it impose any > constraints on memory allocation? Does it suffer from poorer garbage > collection or allocation performance at the expense of its strategy? > > Thanks, > Phil > -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
