I attached both servers to a Java Profiler (JProfiler). There I can
see that org.hibernate.Criteria.list() consumes much resources.
100 calls to that method take 27sec in tomcat and 11sec in Jetty5.
When I attach the profiler to trace method calling, the difference is
adjusting (85sec vs. 72sec). It does not look like there is any
difference on the methods that both servers use. Just the time spent
working seems to be different.
Could it be a logging issue with those servers?
M.
Am 23.06.2008 um 12:38 schrieb Massimo Lusetti:
On Mon, Jun 23, 2008 at 8:13 AM, Moritz Gmelin
<[EMAIL PROTECTED]> wrote:
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?
I must say i've never used tomcat in production, always jetty, but
this sound strange anyway. Could you provide more infos, did you use a
profiler or something else?
--
Massimo
http://meridio.blogspot.com
---------------------------------------------------------------------
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]
