there are two things to take into account: memory and network like martijn said, a session is too big when it is greater then available heap/target number of users
if you are using session replication for clustering or failover the session is too big when the time to replicate it becomes a bottleneck. -igor On Mon, Jun 15, 2009 at 4:34 AM, Steve Swinsburg<[email protected]> wrote: > Hi all, > I'm monitoring my Wicket app via the RequestLogger and going through making > improvements where needed. I am wondering what > the size of a session would be before it is considered too large? Is the value given in the 'sessionsize' attribute > of the logging output a reasonable way to judge what's good and what's not? > For example, on a particularly large page, rendering a list of data from the > DB: > - 4000 items all at once, no paging = 5071985 bytes, 22854 ms > - add paging, limit to 15 items per page: 35684 bytes, 2213 ms > Obviously the latter is better, but the question is is 35k for a session ok? > What would be the value that it becomes too large? > > For reference and for anyone wondering about how to turn on the > RequestLogger, in your Application class: > getRequestLoggerSettings().setRequestLoggerEnabled(true); > > cheers, > Steve > > > > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
