Details
Description
We run into a disc and cpu bottleneck on a wicket page with 10000+ users, that uses ajax updates via polling (AjaxSelfUpdatingTimerBehavior).
The result of our investigation is that page store needs about 10ms for serialization, while the framework serializes the same data again and again.
Our application doesn't touch the page, but the AbstractPageManager does:
IManageablePage page = getRequestAdapter().getPage(id);
if (page != null)
{
getRequestAdapter().touch(page);
}
Therefore the requested page is always touched, but we couldn't figure out why. If it's possbile not to touch the page here (in some cases) that would solve the problem.
Attachments
Attachments
Issue Links
- breaks
-
WICKET-5943 Wicket Examples Modal Window - the OK/Cancel links do not update the feedback message
-
- Resolved
-
- contains
-
-
- Resolved
-
- is related to
-
-
- Resolved
-
-
-
- Resolved
-