How is the performance of Tapestry?
My own testing, documented in the Sept. 2001 issue of the Java Report, agrees with other testing (documented in the Tapestry discussion forums): Although straight JSPs have a slight edge in demo applications, in real applications with a database or application server backend, the performance curves for equivalent Tapestry and JSP applications are identical. Tapestry has a performance advantage in that it uses a very coarse-grained pooling strategy (pooling entire pages), whereas JSPs burn a fair number of cycles pooling individual JSP tags. Tapestry 4.0 trades slightly longer start up time for improved runtime performance, since it makes much less use of Java reflection. Except in the most extreme cases, application performance is gated by the database. Tapestry gives your developers the time they need to analyze and fix those kinds of problems, rather than getting bogged down in the user interface layer.
