-
Bug
-
Resolution: Obsolete
-
Critical
-
None
-
7.1.0.DR7, 7.1.0.DR8, 7.1.0.DR9
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.
- incorporates
-
WFCORE-2927 Cut the number of java.util.RegularEnumSet used for attribute and operation flags and ModelTypeValidators
- Resolved
- is cloned by
-
WFLY-7728 Increased Memory footprint in recent builds
- Closed
- is related to
-
JBEAP-8911 Sharply increased memory consumption (+ ~50 MB) in full profile in EAP 7.1.0.DR12
- Closed
-
JBEAP-11495 Cache configuration services should start on-demand
- Closed
-
WFLY-7731 Lots of clustering builder instances are left in memory after objects are "built"
- Closed
- relates to
-
JBEAP-7115 Increased startup time in EAP 7.1.0.DR8
- Closed
-
WFCORE-3145 Comment out unused Logger methods
- Resolved
-
WFCORE-3146 Prevent default loading of legacy ManagementXml and AuditLogXml impls
- Resolved
-
WFCORE-3150 Avoid multiple loading of ParallelBootOperationContext
- Resolved
-
WFCORE-3297 Reduce the size of the logging subsystem parsers
- Resolved
-
JBEAP-12563 Comment out unused Logger methods
- Closed