It is possible to set more JVM parameters, but that's the wrong end to start at. Much more important is to profile the code to identify where time is being spent. Without this information, any tuning effort is likely to haphazard.
Since there is no data available, its hard to rule out any of the myriad possibilities. Its fatal to make any assumptions, so many things need to be checked/doublechecked. Is the application cpu-bound? If paging/swapping (insufficient real mem) or pausing for GC a lot, or then it shouldn't be cpu-bound. If the application is cpu-bound, then is it in application code, or java3d/jvm libraries, or OpenGL? Use of -Xserver can benefit application code (as well as have sideeffect of modifying some of the memory management parameters). A useful starting point are the following two URLs: http://java.sun.com/docs/hotspot/VMOptions.html http://wireless.java.sun.com/midp/articles/garbagecollection2/ There are other relevant hotspot documents too: http://java.sun.com/docs/hotspot http://java.sun.com/docs/hotspot/gc/index.html -- ============================================================================ ,-_|\ Richard Smith - SE Melbourne / \ Sun Microsystems Australia Phone : +61 3 9869 6200 [EMAIL PROTECTED] Direct : +61 3 9869 6224 \_,-._/ 476 St Kilda Road Fax : +61 3 9869 6290 v Melbourne Vic 3004 Australia =========================================================================== =========================================================================== To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff JAVA3D-INTEREST". For general help, send email to [EMAIL PROTECTED] and include in the body of the message "help".
