Hi all, any performance comparison out there between Spring MVC and Wicket?
I do want to convince people I'm working with to use Wicket for the next presentation projects but someone has concerns about the session usage and performances with Ajax. There are a lot of post in which is explained this is not a problem and for example I know using Detachable models is the first best practice for the first problem but I want to show numbers to my colleagues... :-) To compare the memory usage performance I wrote the same simple application in Wicket (Detachable Models used) and Spring MVC. Both are using the same service layer (Spring + Hibernate) to retrieve objects from the db; in the applications there are two stateless pages: the first one is just a list page without pagination and the second one is a detail page. In the database there are 50 elements and I wrote a JMeter script in which a request for each page is done (a CookieManager is used to create always a new session) , 10 threads are used with 1 sec of ramp up and 20 loops per threads. Each application is deployed "alone" in a JBoss instance. Then I launch the Jmeter script and use JConsole for the memory analysis. Something wrong with this? Any Suggestions (more elements in the db, more threads, more something...)? Thanks a lot, Vicio. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
