I prefer using ejbql queries. for queries that returns a lot of elements, i do
not retrieve all the elements, i uses pages. My gui is not able to display all
the elements in once, so the cost of the query is hide by the time needed by
the user to request the next page.
It is probably easier to
Setting hibernate logging to WARN does help but there is still a signficant
performance difference.
Here are the elapsed times with 20 consecutive selects each returning 5000
different rows (averaged over 3 runs excluding the 1st run). Hibernate logging
set to WARN.
createQuery(hsql): 11088ms
If you turn hibernate logs off, is it always so slow ?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3988441#3988441
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3988441
___
Following your suggestion, I tried setting FlushModeType to COMMIT (the only
other value supported with EJB3) as follows, but the query is as slow as before.
| public List< TestData > select( int accountId, Timestamp timeScheduled
) {
| Query query = em.createNativeQuery( "s
See
http://jira.jboss.com/jira/browse/EJBTHREE-326
and
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=68954&postdays=0&postorder=asc&start=0
Problems is around the flush. If you perform a query with EJB3, a fluish is
performed automatically before. It looks like that issues has been f
