Details
-
Type:
New Feature
-
Status: Resolved
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: EE-4.2.0.GA
-
Component/s: Core Extensions
-
Labels:None
-
Environment:all
Description
Issue Links
- blocks
-
ICE-11113
Optimize ICEfaces memory consumption
-
- Closed
-
Activity
| Assignee | Mircea Toma [ mircea.toma ] |
| Fix Version/s | EE-4.2.0.GA [ 13071 ] |
| Repository | Revision | Date | User | Message |
| ICEsoft Public SVN Repository | #49343 | Thu Oct 06 09:20:53 MDT 2016 | mircea.toma | |
| Files Changed | ||||
MODIFY
/icefaces4/trunk/icefaces/core/src/main/java/org/icefaces/util/EnvUtils.java
|
| Summary | Profile state saving to potentially improve memory consumption | Implement custom state manager to improve cpu & memory consumption |
| Description | Profile state saving to potentially improve memory consumption and reduce component creation and disposal. | Implement custom state manager to improve cpu & memory consumption. The state manager will avoid serialize and deserialize the state of the component tree. This will also reduce component creation and disposal. |
| Attachment | custommemoryusage.tiff [ 22314 ] | |
| Attachment | customstatesaving.tiff [ 22315 ] | |
| Attachment | customviewrendering.tiff [ 22316 ] | |
| Attachment | partialstatesaving.tiff [ 22317 ] | |
| Attachment | standardmemoryusage.tiff [ 22318 ] | |
| Attachment | standardviewrendering.tiff [ 22319 ] |
| Comment | [ !standardviewrendering.tiff! ] |
| Attachment | custommemoryusage.tiff [ 22314 ] |
| Attachment | customstatesaving.tiff [ 22315 ] |
| Attachment | customviewrendering.tiff [ 22316 ] |
| Attachment | partialstatesaving.tiff [ 22317 ] |
| Attachment | standardmemoryusage.tiff [ 22318 ] |
| Attachment | standardviewrendering.tiff [ 22319 ] |
| Attachment | custommemoryusage.png [ 22320 ] | |
| Attachment | customstatesaving.png [ 22321 ] | |
| Attachment | customviewrendering.png [ 22322 ] | |
| Attachment | partialstatesaving.png [ 22323 ] | |
| Attachment | standardmemoryusage.png [ 22324 ] | |
| Attachment | standardviewrendering.png [ 22325 ] |
After running the CPU and memory profiling the custom state manager proves to be more CPU perfomant but it uses more memory than the default partial state management.
Here is how much time the state managers spend on saving/restoring the state. The default state manager spends approximately 50000 ms to save/restore state for 55 requests. The custom state manager is spending just 191 ms. So the state saving& restoring performance is increased 26 times.
default state manager
custom state manager
The following profiling results show how much time state management is spending relative to page rendering. The default state manager spends 27.3% restoring the state while the custom state manager spends ~0%.
default state manager
custom state manager
Memory wise the custom state manager does not do so well since the entire component tree is kept in the session, not its serialized form. The custom state manager uses ~40MB per session while the default (delta) state manager uses just ~17MB per session.
default state manager
custom state manager
Added Wiki documentation.
| Status | Open [ 1 ] | Resolved [ 5 ] |
| Resolution | Fixed [ 1 ] |
| Summary | Implement custom state manager to improve cpu & memory consumption | New View Root State Manager to improve cpu & memory consumption |
Added new state manager implementation that does not de/serialize the component tree to restore/save the state of the view. Instead it keeps the UIViewRoot as the representation of the view. Restoring the view state is as simple as replacing the current UIViewRoot object.
Introduced to new context parameters:
Parameter used to enable the custom state manager. The default value is false.
Sets maximum number of views allowed to exist for a given session when custom state manager is enabled. Default value is 15.