[
https://issues.jboss.org/browse/WFCORE-2083?page=com.atlassian.jira.plugi...
]
Tomaz Cerar updated WFCORE-2083:
--------------------------------
Description:
Profiler shows that we lots of duplicate object allocations with empty arrays
It also shows that lots of our builder objects are kept in memory even after builder did
its job and created the object.
There are also cases where inner classes should be static to prevent capturing object
reference to be kept
and many other cases.
was:
In our test scenario (see below) memory footprint has been increased between EAP 7.0.0.GA
and current EAP 7.1.0.DR7 for more than 8% (~8MB) for Full profile and more than 9%
(~6.5MB) for web profile. Could you please comment whether this is intended.
Test scenario:
# Start EAP instance.
# Measure its memory footprint - try to get the lowest possible footprint, that means
force garbage collection a few times right before measuring. We enforce GC 10 times.
We see an increase both in heap size (~ 29 vs. 34 MB) and the metaspace size (~ 64 vs. 68
MB) - these numbers are for standalone-full profile.
Reduce number of object allocations and memory footprint
--------------------------------------------------------
Key: WFCORE-2083
URL:
https://issues.jboss.org/browse/WFCORE-2083
Project: WildFly Core
Issue Type: Bug
Components: Modules, Server
Affects Versions: 3.0.0.Alpha14
Reporter: Tomaz Cerar
Assignee: Tomaz Cerar
Priority: Critical
Profiler shows that we lots of duplicate object allocations with empty arrays
It also shows that lots of our builder objects are kept in memory even after builder did
its job and created the object.
There are also cases where inner classes should be static to prevent capturing object
reference to be kept
and many other cases.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)