memory performance issue in java engine

[Former Member]

HI Gurus,

i would like to know about the what are performance issues in java stack ?

please help me ...

Thanks

Anki.

[Former Member]

Hi Anki,

Please refer to Java Server Troubleshooting Guide, a very best start to understand different problems and solutions.

http://wiki.sdn.sap.com/wiki/display/JSTSG/JavaServerTroubleshootingGuide%28JSTSG%29

Br,

Venky

[Former Member]

Hi Anki,

check out the following guides:

1) java performance tuning for beginners : https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/b0e0d894-0cc9-2b10-5893-a21fe39c...

2) fine tune j2ee engine: https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/7fdca26e-0601-0010-369d-b3fc87d3...

3)WEB Application server performance analysis : https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/66aad990-0201-0010-a296-c582b6e8...

The follwing web-site contains valuable tips regarding tuning : http://www.javaperformancetuning.com/tips/

Regards,

Sravanthi

[Former Member]

Hi,

One of the main performance issue is OutOFMemory error and slowness in the response.

To start with you can fine tune Heap Memory parameters,Garbage collection parameter and add additional server nodes if you have sufficient hardware available.

You can refer to troubleshooting guides,which are available in plenty

Regards,

Ashutosh

[Former Member]

Hi Anki,

Main performance issue that i hve observed in Java stack are slow response,Thread not releasing memory hence causing OutOfMemory situation.

You can look at tuning heap memory parameters such as -XX:MaxPermSize,-Xmx refer to this link:

http://help.sap.com/saphelp_nwesrce/helpdata/en/97/d0de42c02c420da92a7cec346f9168/content.htm

Also check forum:

which talks about same thing.

Regards,

[Former Member]

Hi,

to avoid the commum outOffMemmory error, sometimes its needed to perform periodical (daily)

restars of the java engine, because even if you increase heap size, or add more server nodes, the garbage collector doesnt alllway clean 100% of unused memory, so along the time the memory usage keep going up, until it reachs the maximum heap size of the server node, and causes a server node restart.

daily "cleansing" restarts are a workaround for this situation.

best regards,

Ricardo

[Former Member]

Hello Anki,

You need to analyse your core dump , thread dump in order to identify the root of the problem.

After knowing the faulty class file name / component you can resolve the issue permanently.

Restarting will clear the memory but considering SLA it might not get approval from business.

Regards.

Sumanta

[AntalP]

you need to trigger heap dumps and analyse it with MAT http://www.eclipse.org/mat/

you can check the time of GCs, the minor GCs should take >1sec, the full GCs should take >10sec