Hi,
I am doing some experimentation with Hibernate and EJB3 and have noticed if I run a simple query using entityManager.createQuery() it is several times slower than a standard hibernate session.createQuery() executing the same query string.

I am timing the actual hibernate call itself (not serialisation etc.) so i can't explain the differences....
--------------------------------------
long starMillis = System.currentTimeMillis();
List<Job> temp = entityManager.createQuery("from JobBean WHERE completionDate IS NULL AND isClosed = false AND deleted = false ORDER BY id").getResultList();
long endMillis = System.currentTimeMillis();

log.info("Adding " + temp.size() + " jobs in " + (endMillis-starMillis) + "mS");
--------------------------------------

and

--------------------------------------
long starMillis = System.currentTimeMillis();
List<Job> temp = session.createQuery("from JobBean WHERE completionDate IS NULL AND isClosed = false AND deleted = false ORDER BY id").getResultList();
long endMillis = System.currentTimeMillis();

log.info("Adding " + temp.size() + " jobs in " + (endMillis-starMillis) + "mS");
--------------------------------------

The EJB is running in GlassfishV2 and the hibernate session version is running in a JSE application. The PU and hibernate.cfg.xml have the same parameters etc..

The Session bean/EntityManager takes 47.6 seconds to retrieve 3216 jobs and the standard JSE/session takes a mere 6.7 seconds - so the difference is nontrivial.


Has anyone experienced anything similar?

Just a quick update...

I tweaksed the app server settings and changed the driver to the PooledConnection variant (I'm using PostgreSQL).

The EntityManager timings are now around 22-24 seconds, still a very large difference.

The only other change asside from the EntityManager Vs raw hibernate session is the EntityManager entities utilise interfaces and make use of the @Target(class) annotation to identify the implementation class - asside from that the models are the same.

Still confused as to what is causing the performance problem....

Any help and pointers appreciatted.

Thanks

Just a quick update...

I tweaksed the app server settings and changed the driver to the PooledConnection variant (I'm using PostgreSQL).

The EntityManager timings are now around 22-24 seconds, still a very large difference.

The only other change asside from the EntityManager Vs raw hibernate session is the EntityManager entities utilise interfaces and make use of the @Target(class) annotation to identify the implementation class - asside from that the models are the same.

Still confused as to what is causing the performance problem....

Any help and pointers appreciatted.

Thanks

Just a quick update...

I tweaksed the app server settings and changed the driver to the PooledConnection variant (I'm using PostgreSQL).

The EntityManager timings are now around 22-24 seconds, still a very large difference.

The only other change asside from the EntityManager Vs raw hibernate session is the EntityManager entities utilise interfaces and make use of the @Target(class) annotation to identify the implementation class - asside from that the models are the same.

Still confused as to what is causing the performance problem....

Any help and pointers appreciatted.

Thanks

Well, I can't provide any pointers per se, but I did want to say that I'm finding you posts interesting. Keep us informed!

Switching over to the similiar thread I have under the EntityManager et al forum:

http://forum.hibernate.org/viewtopic.php?t=988354

Entitymanager also run in JSE application. Try query with EntityManager but without using any ejb container. I mean try it in jse application and compare the results.