> In my company , we built a really nice employment exchange with wicket and > we cant wait to launch it. But we need to know that assuming one sticks to > the best design practice of wicket (using detachable models everywhere and > stateless pages where necessary), is it so much memory and processors we > need to buy to make it worth it or what?
It's perfect you already build an application. The best thing you can do is start doing load tests (e.g. use JMeter or look at the wicket-threadtest project) and measure how much your application needs for how many sessions and define your scale up and out strategy accordingly. > Present Wicket - Wicket 1.2.4 Note that Wicket 1.3's default session store implementation is a reduced RAM usage *a lot* for the price of a bit more processor utilization and file access (in the app I'm using this is typically 1 - 10 mili seconds per request). ------------------------------------------------------------------------- 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 [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user
