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:

• com.icesoft.viewRootStateManager
  Parameter used to enable the custom state manager. The default value is false.

• com.icesoft.viewRootStateManager.maxViews
  Sets maximum number of views allowed to exist for a given session when custom state manager is enabled. Default value is 15.

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.