Fridolin Jackstadt created WICKET-5933:
------------------------------------------
Summary: Avoid serialization of untouched page after ajax request
Key: WICKET-5933
URL: https://issues.apache.org/jira/browse/WICKET-5933
Project: Wicket
Issue Type: Improvement
Components: wicket
Affects Versions: 6.19.0
Reporter: Fridolin Jackstadt
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:
{noformat}
IManageablePage page = getRequestAdapter().getPage(id);
if (page != null)
{
getRequestAdapter().touch(page);
}
{noformat}
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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
