On Tue, Feb 15, 2011 at 8:27 AM, Suraj Chandran <[email protected]> wrote: > 10K concurrent sessions.
That really is not a problem IMO. If you have a 2GB heap: you probably should reserve 1GB for request processing, and 1GB for session/cache/etc storage. However, memory is not that expensive anymore, and it is fairly easy to get a 4GB or more machine up and running for a small amount of €... 1GB/10kB = 100kB/session Tuning the session handling of your container (shorter time-to-live means less burden on your server, swapping out sessions that haven't been used for ~5/10 minutes to disk), working with bookmarkable page URLs to prevent session time outs annoying your users, ensuring you use LoadabeDetachabeModels and PropertyModels instead of static models it should be easy to get much less session usage than 100kB/session. Martijn -- Become a Wicket expert, learn from the best: http://wicketinaction.com --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
