Don't forget that each Tile is a jsp that need to be compiled at the first hit,
like all jsp. This happen normally only once when you change the jsp content.
After that, performances overhead is not significant. There should be something
wrong in your config.
Cedric
Andy Noble wrote:
If content/functionality is relatively static (and you are not deploying to
unknown containers), JSPs should really be precompiled by the container JSP
compiler (Jasper in Tomcat) and included in the jar deploy file.
Mark
-Original Message-
From: Cedric Dumoulin [mailto:[EMAIL
I've noticed that the initial compile takes longer, but once the JSP is
compiled, the performance cost should dwindle. The best thing is to run
your own load tests, since a number of factors can affect performance
and scalabilty. It sounds like something else is wrong here.
Andy Noble wrote:
3 matches
Mail list logo
