You should also make sure that you are using DiskPageStore as pagestore. -Matej
On 8/24/07, Igor Vaynberg <[EMAIL PROTECTED]> wrote: > who cares, he says he has a database in there so the tests should be pretty > even. > > for all we know wicket might be five times slower then spring mvc! and it > may very well be because spring mvc is so simple in comparison. but who > cares? a five fold improvement of something that is only five percent of the > request time to start with is insignificant. > > anyway, the only thing to really look for is to make sure the wicket app is > running in deployment mode when you run the tests. there is also a jmeter > page on wiki somewhere if you want more clues. > > -igor > > > On 8/24/07, Matej Knopp <[EMAIL PROTECTED]> wrote: > > > > There is not much point in comparing Wicket to Spring MVC. Spring MVC > > is a very simple action based framework with very little functionality > > (and probably minimal overhead). So what you would really be comparing > > is Wicket to JSP (assuming you use JSP as your view layer). Now again, > > Wicket is a full blown component based framework with advanced state > > management, while JSP is a simple templating engine. You're trying to > > compare apples with cars :) > > > > -Matej > > > > On 8/24/07, Vincenzo Vitale <[EMAIL PROTECTED]> wrote: > > > 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] > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
