Some code I am writing right now for a project should make substantial use of the optimizations available in the Server JVM. I tried adding max.jvm.option -Xserver to my max.java.config.txt and from examining the process in VisualVM I see that even though the -Xserver option does seem to be passed, Max is still using the Client JVM.
I tried this with MaxMSP 5.1.9 and Max 6.0.5 on OS X 10.7.4, Java 1.6.0_33.
Is this a bug or an intentional part of the mxj design? I know the server JVM will have longer startup/class loading times and a larger memory footprint, but for this project I suspect the tradeoff would be worth it to gain the additional optimizations. Is it possible to update Max to respect this JVM option?