> will, it means that the JVM needs to be understood by those deploying it. But > guess what, that is the same for just about every machine on the planet.
Except, not every IT org can devote a deployment engineer to understanding the Java memory model and intricate details about generations and collector strategies. This leads to countless real- world developers arbitrarily bumping up memory per trial n' error fashion. And really, if I am given a vmware instance for my server, where the system admins (or the vmware governor itself) can and will tweak available memory, how am I going to specify optimal -X arguments? -- 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.
