java虚拟机分析与优化.ppt

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * I want my application to concurrently with a lot of other JVM’s (hoteling). Use default serial collector as the GC algorithm is single threaded I need my application to perform good on a large number of processors. -XX:+UseParallelGC I need my application to return near constant response times on machines that have a large number of processors. -XX:+UseConcMarkSweepGC I need my application to return near constant response times on machines that have a small number of processors. -XX:+UseTrainGC Runtime Performance TuningWhat GC Policy should I choose for the Sun JVM? * Runtime Performance TuningOther Sun/HP JVM Tuning Parameters -Xincgc - incremental GC, uses the Train algorithm -XX:+AggressiveHeap - maximizes heap size and algorithms for speed -Xnoclassgc - disable class garbage collection -Xss - set the stack size of each thread (512K) -XX:+DisableExplicitGC - no System.gc() will be executed -XX:TargetSurvivorRatio - sets threshold in survivor space for promotion to kick in -XX:+UseAdaptiveSizePolicy - JVM determines good size for Eden, Survivor Spaces (default is on) -XX:+UseISM - allows for bigger pages (4MB) -XX:+UseMPSS (Solaris 9 onwards) - uses Multiple Page Size Support w/4mb pages, replaces ISM -Xoptgc - optimizes GC in Young Generation (HP only) * The tenured space must be large enough to hold all persistent data of the application. Too small will cause excessive GC or even out of memory conditions. For a typical WebSphere Application Server application this is ~100-400Mb. One way to determine the tenure space size is to look at the amount of free heap exists after each GC in default mode %free heap x Total heap size Analyze GC logs to understand how frequently the tenured space gets collected. An optimal generational application will have very infrequent collection in the tenured space.  Runtime Performance TuningHow to tune a generationa