IBM Maximo: Java Virtual Machine Properties for IBM WebSphere
- UI Cluster -> 1 CPU por JVM / 4-6 GB heap / 50-75 Users por JVM
- Cron Cluster -> 1 CPU por JVM / 4-6 GB heap / at lest 2 JVMs
- Integration Cluster -> 1 CPU por JVM / 4-6 GB heap / at lest 2 JVMs
- BIRT Cluster -> 1 CPU por JVM / 4-6 GB heap / at lest 2 JVMs
Variable | Description | Articles |
---|---|---|
-Dsun.rmi.dgc.ackTimeout=10000 | Intervalo para verificar objetos para GC. | |
-Xdisableexplicitgc | Desabilita o system.gc() | |
-Xms | initial heap size. Colocar o valor igual ao Xmx melhora a performance na inicialização. | |
-Xmx | max heap size | |
-Xmn | nursery size igual a 25% da total heap. deve ser definida junto com -Xgcpolicy:gencon | |
-Xgcpolicy:gencon | Registrar as operações SQL que excedem o limite de tempo (milissegundos) | |
Example | Example | Example |
Example | Example | Example |
Increase Heap Size
Application Server
1) in Websphere admin console, 2) go to Servers section -> Server Types -> Websphere Applicaton Servers -> [MXServer] 3) go to Java Process Management (link on the right side menu) -> Process Definition -> Java Virtual Machine. 4) Set both Initial and Maximum heap size to 6144 MB (Production)
Dmgr
1) in Websphere admin console, 2) go to System Administration section (on the left side menu) -> Deployment manager 3) go to Java Process Management (link on the right side menu) -> Process Definition -> Java Virtual Machine. 4) Set both Initial and Maximum heap size to 2048 MB (Production)
WAS Admin console
1) edit the wsadmin.bat|sh under [Websphere Home\AppServer\bin\ 2) update this parameter:
PERFJAVAOPTION=-Xms2048m -Xmx2048m –Xquickstart
ejbdeploy.bat - deploy tool
1) edit the ejbdeploy.bat file under [Websphere Home]\\AppServer\deploytool\itp\ 2) update this parameter:
EJBDEPLOY_JVM_HEAP=-Xms2048m -Xmx2048m