On Aug 13, 4:26 am, Alan Kent <alan.james.k...@gmail.com> wrote: > Not a great analogy really is it? I don't know of any widely used OS that > requires every process to say how much memory it's going to use before it > even starts running. > > In fact this post really highlighted to me how restrictive the approach is! > Forget writing an app that can adapt to different inputs dynamically!!! You > have to pick memory size first. No wonder java is only serious for server > side stuff.
Its not as restrictive as it might seem. -Xmx is the max memory the JVM is allowed to take its not what it takes at startup. There is also -Xms which is the start size. Java is not on the desktop since it has serious deployment issues. Once they are solved nobody will complain about things like those flags anymore since they could be easily picked by the launcher (@see NetBeans which picks -Xmx for you). Don't get me wrong, a resizing heap would be nice to have but i bet almost everyone will try to disable it. If we would have it right now we would complain about things like: - eclipse eats all my memory and never frees anything - everytime when i hit "rafactor" the jvm stops, my heap grows and if i stop refactoring the jvm stops again and the heap shrinks.. lets add a feature called -Xmx :) regards, michael > > Alan > > Sent from my iPhone > > On Aug 12, 2011, at 2:37 PM, mbien <biena...@arcor.de> wrote: > > > > > > > > > see it as performance optimisation. A GC impl which would have to deal > > with fragmented, non continuous and resizing heap would have a hard > > time to compete with the current VM. A JVM is a operating system for > > java applications. You can't plug in new RAM brick in your system > > easily at runtime for the same reasons. > > > I would go even further and say that writing java applications with > > unknown memory requirements is not that professional :P > > > On Aug 12, 2:48 pm, phil swenson <phil.swen...@gmail.com> wrote: > >>http://eblog.chrononsystems.com/xmx-is-hurting-the-usability-of-java > > >> I've been saying this since I first discovered the terrible > >> OutOfMemoryException in 1999. Xmx makes java inherently unstable. > >> You can't rely on your app to stay up until you find the magic Xmx > >> setting. WTF!? > > >> Dick/Carl/Tor/Joe - when you talk to Mark Reinnhold, can you bring this up? > > > -- > > You received this message because you are subscribed to the Google Groups > > "The Java Posse" group. > > To post to this group, send email to javaposse@googlegroups.com. > > To unsubscribe from this group, send email to > > javaposse+unsubscr...@googlegroups.com. > > For more options, visit this group > > athttp://groups.google.com/group/javaposse?hl=en. -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to javaposse@googlegroups.com. To unsubscribe from this group, send email to javaposse+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
