Session size really depends on the types of models you use. For instance, if you have a list of items in some sort of repeating view, perhaps your model that loads the list is loadable / detachable (good), but you might do something like "new Model(rowItem)" around each item in, for instance, your IDataProvider, which then holds each item indefinitely - storing each item in session (bad).
If you have one page or component that drastically increases session size, you should use a memory profiler to see what your most prolific objects are. You might be surprised at what you're still holding on to. On Mon, Jan 12, 2009 at 9:43 AM, carloc <carlo_ca...@yahoo.com> wrote: > > Hi Everyone, > > RequestLogger - > > time=103,event=Interface[target:AjaxPagingNavigationLink(userListForm:userGroupContainer:userGroupCheckGroup:ajaxPagingNavigation:navigation:9:pageLink), > page: com.ccti.base.web.usergroup.VedUserGroupPage(2), interface: > > IBehaviorListener.onRequest],response=PageRequest[com.ccti.base.web.usergroup.VedUserGroupPage(2)],sessionid=kdrq2wp0eaea,sessionsize=212417,sessionstart=Mon > Jan 12 23:24:44 CST > > 2009,requests=14,totaltime=7024,activerequests=1,maxmem=66M,total=18M,used=14M > > sessionsize=212417 > > I'm particularly interested of the sessionsize that is being logged by the > requestlogger. > I was wondering what size does it contain? > > In One of My List Pages, > It increases by about 72000 when I put in an ajaxpagingnavigator. > > I was just wondering what things are put into the session? > One thing that bothers me though is I tried using a LoadableDetachableModel > in my dataview. > It returned the almost the same sessionsize for a dataview in which I used > a > CompoundDetachableMOdel. > > I tried viewing the page map using eclipse's debug, I can see that it keeps > a reference to the previous page, so does it mean that Wicket always keeps > the last page available in the HttpSession? or does it keep the current > page > in the session. > > If I try exploring the session, I can see that the loadableDetachableModels > model object cannot be viewed. > And the compoundpropertymodel's attributes can be viewed. > > As far as I can see, the wicket components consume significant session size > . Please correct me if I am wrong. > > > So question is, > > What Page Does Wicket Store in its HttpSession? How Many Pages Does It > Store? > What consumes significant session size in wicket? > Is it bad to keep a reference to the previous pages in instance variables > of > new pages? > > Carlo > -- > View this message in context: > http://www.nabble.com/sessionsize-of-requestlogger-tp21416562p21416562.html > Sent from the Wicket - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > -- Jeremy Thomerson http://www.wickettraining.com
