Hi, Check https://cwiki.apache.org/confluence/display/WICKET/Page+Storage Only the last used page is stored temporarily in the http session. Detaching the models decreases the used memory.
On Thu, Nov 22, 2012 at 12:09 PM, tobi <tobias.gie...@code-sourcery.de>wrote: > Hi guys, > > From my understanding & experiments with Wicket's built-in session > inspector , detaching models seems to just affect the size of the page > store (and of course cut-down the amount of I/O required for serializing > the object graph). The session size shown on my pages is a constantly low > value (<1k , we're storing nothing except the currently logged-in user). > > So it *seems* not detaching models has no effect on the (long-term) memory > footprint of a Wicket application. > > According to https://cwiki.apache.org/**WICKET/working-with-wicket-** > models.html<https://cwiki.apache.org/WICKET/working-with-wicket-models.html>, > not detaching models should affect the session size but at least looking > at the inspector I can't see this. Is the wiki article still correct / the > inspector not telling the truth ? > > Thanks, > Tobias > > P.S. I'm using Wicket 1.5.8 btw > > ------------------------------**------------------------------**--------- > To unsubscribe, e-mail: > users-unsubscribe@wicket.**apache.org<users-unsubscr...@wicket.apache.org> > For additional commands, e-mail: users-h...@wicket.apache.org > > -- Martin Grigorov jWeekend Training, Consulting, Development http://jWeekend.com <http://jweekend.com/>
