Are these jvm args of jvm 1.4 suitable for jvm 5?

1.We used following mem_args with jvm 1.4 and weblogic 8.x. Recently we upgraded to wls 9.2 and jvm 5.x. Please suggest me whether following mem args still suitable with jvm 5 for better performance. If not, advise me required changes for better performance.

USER_MEM_ARGS=" -Xmx512m -Xms512m -XX:+PrintGCTimeStamps -XX:+PrintGCDetails -XX:+PrintHeapAtGC -XX:MaxNewSize=24m -XX:NewSize=24m -XX:SurvivorRatio=128 -XX:-UseParNewGC -XX:+UseConcMarkSweepGC -XX:+CMSPermGenSweepingEnabled -XX:+CMSClassUnloadingEnabled -XX:MaxTenuringThreshold=0 -XX:CMSInitiatingOccupancyFraction=60 -XX:PermSize=128m -XX:MaxPermSize=128m -Xloggc:${WL_DOMAIN}/logs/memory_${SERVER_NAME}.log"

2. I'm new to java tuning concept and I would like to tune the jvm/GC settings in my application running in wls 9.2 and jvm 5. Please let me know how to start with tuning analysis/implementation. What is the best tool for tuning?

Thanks a lot!

[941 byte] By [tech_luvera] at [2007-11-27 7:52:36]
# 1

Yes, the above args still apply to J2SE 5.0 and should work fine. The one that I would questions is -XX:-UseParNewGC, which disables the parallel young gen collector. There's usually no need to disable it unless you tripped on a bug. If so, the bug may be fixed in 5.0 so I'd try enabling it again.

As far as tuning, a good place to start is to decide what you want to improve :-).

You're using the Concurrent Mark Sweep (a.k.a. CMS) collector so you are very likely interested in pause times. Do you need still shorter pause times? Or are pause times OK and you want higher throughput? Or, the usual response, both!

Once you've done that, then see the 5.0 GC tuning guide at

http://java.sun.com/docs/hotspot/gc5.0/gc_tuning_5.html

Message was edited by:

jxc

jxca at 2007-7-12 19:33:49 > top of Java-index,Java HotSpot Virtual Machine,Specifications...