Re: Wicket and Spring MVC compared.
I think it's looking okay, did you pick up the thing mentioned on the wiki? You are not using ajax in Spring MVC? It would be wrong to just plain compare non ajax to ajax.. Also you could write to the Jmeter list, to get a broader view of your test plan. Also you'll post results here ? regards Nino Vincenzo Vitale 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]
Re: Wicket and Spring MVC compared.
Hi Nino, at the moment I don't want to compare Ajax so in the applications I wrote for testing it's not used. Sure, I will post the results here... probably the next week... Attached the JMeter scripts I wrote (it would be better only one script but at the moment the urls used are different). I will post them also in the JMeter user list. Thanks, V. On 8/24/07, Nino Saturnino Martinez Vazquez Wael [EMAIL PROTECTED] wrote: I think it's looking okay, did you pick up the thing mentioned on the wiki? You are not using ajax in Spring MVC? It would be wrong to just plain compare non ajax to ajax.. Also you could write to the Jmeter list, to get a broader view of your test plan. Also you'll post results here ? regards Nino Vincenzo Vitale 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]
Re: Wicket and Spring MVC compared.
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]
Re: Wicket and Spring MVC compared.
Yes I see your point and you are absolutely right but please consider that a lot of companies (included mine) have been using Spring MVC for a long time and there are a lot of projects already in production using that technology and working fine with the IT infrastructure now available. Of course IT architects and managers want to know which impact a change can cause also to be able to perform the correct actions during the migration (more ram, improving the clusters, firing developers because with Wicket things are simple... :-) ). Ciao, V. 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]
Re: Wicket and Spring MVC compared.
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]
Re: Wicket and Spring MVC compared.
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]
