Hi again,
I could nail this problem down to the hibernate level.
Executing hibernate queries takes 2-5 times longer when an application
is hosted on tomcat than when it is hosted on jetty5.1.10.
Does anyone have an explanation on that? Is this a pure hibernate
problem or rather in tapestry-hibernate integration?
M.
Am 20.06.2008 um 15:00 schrieb Moritz Gmelin:
Hi,
I have a 5.0.13 application running that handles some grids with
about 150 entries fetched from a database.
Now on one page, this grid is basically the only component of the
page. On another page, there are some beans around that grid and the
grid itself is in a block that is only displayed under certain
circumstances.
Now if this application is run with tomcat 6.0.14, the page where
the grid is one of many components is way slower to render that the
page where the grid is the only component (~3sec vs. <1sec.)
Running the application with jetty 5.5.11 does not show this effect.
The pages are both rendered instantly. With Jetty 6.1.11 again I can
see that the grid contained in the more complex page takes as long
as with Tomcat.
This difference in render times also happens when the grid is shown
as an inPlace grid.
Does anyone see a reason why rendering a component takes so much
longer with Tomcat or Jetty 6 than with Jetty 5 ? Is there anything
I can do to make tomcat faster?
Thanks
Moritz
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
