this is generally in sync with what i know about session usage. if you're using 1.3 and detachable models and so forth, 20K sessions on a reasonable box is not going to be a problem. wicket pages really are pretty small. a very complex one might be 50-100K and i've never actually seen one much over about 100K myself. and since 1.3 pages everything but the most recent page to disk, you've got maybe 50K per session. complex pages could be 80-100K, but simpler pages can also be 15K or less. if you take 50K as an average, that's 20 per MB * 1GB (1,000 MB) = 20,000.
Steven Zou wrote: > > Hi,Maciej,really? it's so exciting. > we're choosing framework now,and I prefer wicket, but the heavy session is > my care. > but there're some questions: > (1)where you result from? Is the 20,200 reality request and not from > jmeter(or other stress test tool)? > (2)300MB/20,000=15KB,Does it mean only 15KB per session? I think 15KB > isn't enough for only one page. > (3)Would you like give us some experience for so high load web > application? > > thanks. > > > Maciej Andreas Bednarz wrote: >> >> Hello Jeremy, >> >> try also to disable any versioning and use read only models. I have tuned >> my private wicket project this way and it now supports more than 20.000 >> concurrent sessions on a single tomcat server. If everything in your >> model is serializable you can also use tomcats disk or jdbc persistence >> store for sessions. There is also a terracotta project, so you can >> cluster your wicket (1.3) application lineary. My average memory usage >> with 20.000 sessions in memory and very complex page structures (multiple >> including page object levels) is about 300MB. I think this could serve >> even a large community site :-) >> >> Maciej >> ----- Original Message ----- >> From: Igor Vaynberg >> To: [EMAIL PROTECTED] ; >> wicket-user@lists.sourceforge.net >> Sent: Thursday, May 03, 2007 7:27 AM >> Subject: Re: [Wicket-user] Sessionless Wicket? >> >> >> detachable models are a must. >> >> in my experience a wicket page is only about 50kb on average. that >> would hardly cause an OOME on a server. 1.3 has second level session >> store that pages to disk, so that is something else you might want to >> try. >> >> once you convert to detachable models oomes should go away. >> >> there is an example in wicket-examples on stateless stuff if you need >> to go that far. >> >> -igor >> >> >> >> >> On 5/2/07, Jeremy Thomerson <[EMAIL PROTECTED]> wrote: >> I know that I read somewhere that there is, or is going to be, a way >> to run your wicket application without creating a session (until >> absolutely necessary). We have a site that has mostly been converted to >> Wicket now, and almost all of it is state-less data.... The URLs are all >> bookmarkable (98% of them are), so there is not much state to track. We >> don't need a full object graph of all your pages and components, except >> for on very few pages once you have signed in. >> >> We're experiencing out of memory problems increasingly with an >> increase in traffic. I'm not holding much in the session, but objects >> are held in pages and components.... I now believe we should have used >> detachable models for many things rather than directly holding a >> reference to a DB-backed object. Should I start by going back and >> retrofitting many of those private references within components to use >> detachable models so that the objects are not held in memory? >> >> Any other suggestions? >> >> Thank you! >> Jeremy Thomerson >> texashuntfish.com >> >> >> >> >> ------------------------------------------------------------------------- >> This SF.net email is sponsored by DB2 Express >> Download DB2 Express C - the FREE version of DB2 express and take >> control of your XML. No limits. Just data. Click to get it now. >> http://sourceforge.net/powerbar/db2/ >> _______________________________________________ >> Wicket-user mailing list >> Wicket-user@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/wicket-user >> >> >> >> >> >> >> ------------------------------------------------------------------------------ >> >> >> >> ------------------------------------------------------------------------- >> This SF.net email is sponsored by DB2 Express >> Download DB2 Express C - the FREE version of DB2 express and take >> control of your XML. No limits. Just data. Click to get it now. >> http://sourceforge.net/powerbar/db2/ >> >> >> ------------------------------------------------------------------------------ >> >> >> _______________________________________________ >> Wicket-user mailing list >> Wicket-user@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/wicket-user >> >> ------------------------------------------------------------------------- >> This SF.net email is sponsored by DB2 Express >> Download DB2 Express C - the FREE version of DB2 express and take >> control of your XML. No limits. Just data. Click to get it now. >> http://sourceforge.net/powerbar/db2/ >> _______________________________________________ >> Wicket-user mailing list >> Wicket-user@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/wicket-user >> >> > :) > -- View this message in context: http://www.nabble.com/Sessionless-Wicket--tf3684664.html#a11754372 Sent from the Wicket - User mailing list archive at Nabble.com. ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
