The comparison is somewhat unfair, since Wicket is the only component-based framework (that have to build a component tree, evaluate events, etc.).
The others are action-based frameworks, which are, basically, syntax sugar to println(). On Tue, May 31, 2011 at 8:24 AM, Ron Smits <[email protected]> wrote: > Interesting, when I check it out and look at the resulting html there are > links to images that are not found, this will generate slowness too > > Ron > I Haven't Lost My Mind - It's Backed Up On Disk Somewhere > > > On Tue, May 31, 2011 at 11:53, Martin Grigorov <[email protected]> wrote: > >> Thanks for the link! >> >> I see he created Github project with the apps and JMeter script at >> https://github.com/jtdev/blogpost_files >> Now we can improve the app and send pull requests and see what else is >> slow in Wicket itself. >> >> On Tue, May 31, 2011 at 12:33 PM, Sebastian <[email protected]> wrote: >> > There is a new performance comparison of Rails, Wicket, Grails, Play, >> Lift, >> > JSP: http://www.jtict.com/blog/rails-wicket-grails-play-lift-jsp/ >> > >> > I find the test results for Wicket difficult to interpret. Looks like the >> > latest trunk has compared to Wicket 1.5RC3 some (new) performance issues >> - >> > maybe since WICKET-3740? >> > >> > Seb >> > >> > >> >> >> >> -- >> Martin Grigorov >> jWeekend >> Training, Consulting, Development >> http://jWeekend.com >> >
