[
https://jira.jboss.org/jira/browse/JBIDE-5838?page=com.atlassian.jira.plu...
]
Dominik Pospisil commented on JBIDE-5838:
-----------------------------------------
I did some basics profiling of SOA-P and EAP with the following results:
- when EAP 5.0 default profile is started and full GC is performed, it occupies ~ 280MB on
heap
- when SOA-P 5.0 default profile is started and full GC is performed, it occupies ~ 480MB
on heap
Also, I did some testing with seam dvdstore and booking examples and I would say that for
devel purposes:
For EAP 5.0, 512mb max heap size is sufficient.
For SOA-P 5.0, 512mb is NOT sufficient, but 768 is.
Default launch configuration for EAP 5.0 and SOA-P 5.0 should have
max heap -Xmx value increased to 768m
--------------------------------------------------------------------------------------------------------
Key: JBIDE-5838
URL:
https://jira.jboss.org/jira/browse/JBIDE-5838
Project: Tools (JBoss Tools)
Issue Type: Bug
Affects Versions: 3.1.0.CR2
Reporter: Dominik Pospisil
Assignee: Max Rydahl Andersen
Fix For: 3.1.0.CR2
Default launch configuration for EAP 5.0 and SOA-P 5.0 have max heap -Xmx value set to
512m. This is too low, both platforms run.conf defaults to 768MB. Couple of redeployments
on those platforms results in OOMEs or eccessive GB overhead. The -Xmx value should be
changed to 768MB.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira