[jira] [Commented] (WICKET-5933) Avoid serialization of untouched page after ajax request

["Andrea Del Bene (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/WICKET-5933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14599182#comment-14599182 ] 

Andrea Del Bene commented on WICKET-5933:
-----------------------------------------

I'm not sure why AbstractPageManager touches the page inside getPage(int id). I think we can simply remove the if block. I've tried it and and nothing seems to be affected.

> 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
>         Attachments: wicket-touch.zip
>
>
> 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)