WebSphere v6.1 tuning simplified on Solaris 10

I have been working on some simplification for the WebSphere App Server V6.1 performance tuning on Solaris 10 platform and it came to my attention that instead of playing with too many flags there is only one flag should be more than good enough to give the boost needed for performance. However this may not apply to all the work load but I would rather try and determine that and start overriding some of the defaults:

Previously the tuning knobs of interest used to be like following:


  • initialHeapSize= eg. 2048
  • maximumHeapSize= eg. 2048
  • -server
  • -Xmn1024m At least 50% of the heap size; more may be better
  • -XX:-ScavengeBeforeFullGC
  • -XX:MaxTenuringThreshold=
  • -XX:+UseParallelGC
  • -XX:ParallelGCThreads= either equal to number of cpu or on multi core systems set it to somewhere between .5-1xNumber of cores.
  • -XX:+AggressiveHeap
  • -XX:PermSize=
  • -XX:+UseParallelOldGC

All of this can be reduced to just couple of flags and it will give more throughput than this one:
So the new reccomendations are:


  • initialHeapSize= eg. 2048
  • maximumHeapSize= eg. 2048
  • -server May not be needed in most cases
  • -XX:+AggressiveOpts -XX:+UnlockDiagnosticVMOptions -XX:-EliminateZeroing

This will take care of JVM tuning and you should spend time setting the websphere thread pools right.
Let me know if you find it other way...

Comments:

Would these simplied settings also be applicable to WAS 6.0.2 ? Simpler is better...

Posted by guest on March 05, 2007 at 05:00 AM PST #

No ! AggressiveOpts is only available to V 1.5 implementation of JVM. For 6.0.2 which is 1.4 JVM AggressiveHeap is the best choice.

Posted by guest on March 05, 2007 at 11:16 AM PST #

I find using "-XX:MaxPermSize=256m -XX:ParallelGCThreads=4 -XX:+AggressiveOpts -XX:+UnlockDiagnosticVMOptions" in WAS v7 will get worse performance than using default JVM parameter "-XX:MaxPermSize=256m". did you meet problem like this before ? could you please give me some suggestion on how to tuning JVM on solaris. Thanks!
eg.

"-XX:MaxPermSize=256m -XX:ParallelGCThreads=4 -XX:+AggressiveOpts -XX:+UnlockDiagnosticVMOptions" ----- 45 transaction/second
"-XX:MaxPermSize=256m" ---- 52 transaction/second

Posted by Qi Zhang on January 05, 2009 at 12:57 PM PST #

I find using "-XX:MaxPermSize=256m -XX:ParallelGCThreads=4 -XX:+AggressiveOpts -XX:+UnlockDiagnosticVMOptions" in WAS v7 will get worse performance than using default JVM parameter "-XX:MaxPermSize=256m". did you meet problem like this before ? could you please give me some suggestion on how to tuning JVM on solaris. Thanks!
eg.

"-XX:MaxPermSize=256m -XX:ParallelGCThreads=4 -XX:+AggressiveOpts -XX:+UnlockDiagnosticVMOptions" ----- 45 transaction/second
"-XX:MaxPermSize=256m" ---- 52 transaction/second

Posted by louisvuitton handbags on May 27, 2010 at 01:33 PM PDT #

Post a Comment:
Comments are closed for this entry.
About

dkumar

Search

Archives
« April 2014
SunMonTueWedThuFriSat
  
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today