oh yeah, be sure you DO NOT test your wicket app's scalability with wicket in development mode!
wicket does a ton of really inefficient things in development mode. just for example, every single component you construct on every page will have a complete stack trace of the caller that constructed the component attached as metadata. needless to say, that is not cheap (either in time or memory)! Scott Swank wrote: > > I have a quick question about server load, in particular I want to > determine what sort of volume existing applications support. > > We spread our load across 5 JBoss servers and need to support 200 > requests/second (40/second per server). Are other Wicket applications > handling this volume? > > Thank you, > Scott > > -- > Scott Swank > reformed mathematician > > ------------------------------------------------------------------------- > 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/how-busy-a-site-is-wicket-known-to-support--tf3949732.html#a11206648 Sent from the Wicket - User mailing list archive at Nabble.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
