Do you have caching disabled?  If you do, then tapestry is doing all
kinds of extra work on every request in order to detect any changes
that are made to the webapp between requests.  Generally, caching will
be enabled via an environment variable set like this:
-Dorg.apache.tapestry.disable-caching=true but it could easily be in a
startup script or similar, too.  Remove the line entirely or set it to
false and you should see it improve performance dramatically.  The
downside is you'll now have to restart the app to detect any changes
made to the templates, page files, or properties files in the webapp.

--sam


On 12/7/06, Henry Chen <[EMAIL PROTECTED]> wrote:
I'm running Tapestry 4.1.1 snapshot, tomcat 5.5 on two machines. The speed
is kind of slow. I did a test on the workbench sample. The speed is much
slower than browsing the workbench sample on tapestry website. Does anybody
have this issue too? Any suggestions? Thanks a lot!






---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to