Details
-
Improvement
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
9.10.0
-
None
Description
ListenerRequestHandler currently forces initialization of pages. For already initialized stateful pages, this traverses the entire component hierarchy. For large pages, this can be a costly operation.
My profiler shows a significant amount of CPU load coming from these unnecessary traversals:
Forcing page initialization was originally introduced in WICKET-4116 in this commit to fix an issue with expired pages and checking for statelessness.
In WICKET-5083, this commit added the same forced initialization directly to Page.isPageStateless().
I think we can get rid of the initialization in ListenerRequestHandler and rely on the conditional logic in Page.isPageStateless to trigger initialization if necessary.
Attachments
Attachments
Issue Links
- links to