-
Bug
-
Resolution: Obsolete
-
Critical
-
None
-
11.0.0.Alpha1
-
None
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.
- clones
-
JBEAP-6731 Increased Memory footprint in EAP 7.1.0
- Closed
- is cloned by
-
WFCORE-2083 Reduce number of object allocations and memory footprint
- Resolved