The reason the session impacts the scalability of Wicket applications under high load (large numbers of concurrent users) is that Wicket, by default and by design will store the entire component model for a Page (and all pages referenced by that page - and multiple versions of those pages!!) - in the session - in memory. This can very quickly spin out of control unless you are very careful about how you design your Wicket application. (this "PageMap" was originally intended to make applications feel more "desktop" like to facilitate back buttons, different versions of each page, and different views of model data across each version of a page)
T5, on the other hand, only stores a users "working data" (e.g. user name, products ids etc) - not an in memory copy of every page (and version of that page and referenced pages etc...) that they have loaded with the associated components to represent everything on the page (labels, forms... the lot) - which is what Wicket does. Thus - Wicket may or may not render a single page faster than T5 under certain circumstances (according to the 5.0.18 benchmarks above) but it does not mean that it will scale well under high load (for many thousands of concurrent users) without resorting to complex session clustering or very judicious application design which can end up "obfuscating" the code considerably. This is a well known "gotcha" for Wicket newbies. (BTW: I don't mean to denigrate Wicket in any way, it is a great framework, and just to be clear you can still build high load sites using Wicket - but was never a feature of the framework by design from day 1, in the way that page pooling was for T5) Howard Lewis Ship wrote: > > On Tue, May 12, 2009 at 1:00 PM, Neil Curzon <[email protected]> > wrote: >> Well, whether a page view is executed in one framework or another, the >> same >> calls into the service layer should be made, and the same persistence >> queries should be executed. As long as the frameworks' component >> lifecycles >> are co-operative with the design of your application (big if?), the load >> on >> the other tiers should be constant. I think that the relative cost of >> simply >> throwing some plain HTML together, if it is indeed adding 13+ms to every >> request, is relevant. >> >> But yeah, a more advanced web framework may give you the power to >> implement >> a more efficient solution with less development effort. There is a lot of >> grumbling about Tapestry documentation, but Tapestry has Wicket soundly >> beaten there. > > Thanks! There's lots of room for meta-programming in T5 that isn't > present in Wicket. > >> >> All of my page views were done without a session, and it seems that >> Wicket's >> raw performance advantage will only increase when the session comes into >> play. I understand that will come at the cost of scalability via >> clustering >> and memory consumption, though. I do agree that there are many details >> that >> need to be taken into account. >> > > I don't follow you here; I don't see a reason why adding a HttpSession > to the mix would affect either framework more than the other ... until > you hit a cluster, then T5 should (in theory) have an advantage. > >> The problem is that I can't actually compare a real application in >> Tapestry >> vs Wicket without first implementing that application. And, >> unfortunately, I >> can only choose one framework, and must choose one first. >> > > A common problem. > >> Neil >> >> On Tue, May 12, 2009 at 3:23 PM, Christian Edward Gruber < >> [email protected]> wrote: >> >>> >>> On May 12, 2009, at 2:47 PM, Neil Curzon wrote: >>> >>>> I think it should be possible to reason about the web framework >>>> independently from the back end. >>>> >>> >>> >>> However it just ain't so. If the front-ends had equivalent >>> architectural >>> impact, then sure. Or if everything were serial, then sure. However, a >>> front end can behave differently with minimal back-end activity vs. a >>> high >>> degree of back-end activity, simply because it may be able to work or >>> cache >>> work product in one scenario that isn't possible in the other, or where >>> the >>> margins are so tight that such effort is a higher percentage of the >>> total >>> work done. Real end-to-end performance on a request is subject to a lot >>> of >>> architectural constraints, when it comes to measuring, and you can't do >>> a >>> straight-line computation from a no-op case. >>> >>> For example, the design of T5 may be such that a page constructed with a >>> lot of javascript from different components is handled better than with >>> taglibs, since T5 can bundle it up, call it a versioned asset, send it >>> as >>> one single compressed stream, and cache it on the client. If the other >>> framework handles the JS file-by-file, without compression, and has to >>> re-fresh more frequently, then it's possible that T5 can vastly >>> outperform >>> the other in a complex application, by design. >>> >>> cheers, >>> Christian Edward Gruber >>> [email protected] >>> http://www.geekinasuit.com/ >>> >>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [email protected] >>> For additional commands, e-mail: [email protected] >>> >>> >> > > > > -- > Howard M. Lewis Ship > > Creator of Apache Tapestry > Director of Open Source Technology at Formos > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > > -- View this message in context: http://www.nabble.com/Benchmarking-Tapestry-tp23487852p23519734.html Sent from the Tapestry - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
