Surely because of some issue with JPA tab provider. Look at this thread:
I have tested the performance against a 600,000 rows table with JPATabProvider and the response time (as Firebugs says) is around 600 ms, for querying and drawing the corresponding html, including the count. I tried with JDBCTabProvider and the performance is just the same. I tested using an AS/400 as database.
Therefore, the performance of JPATabProvider with huge tables is very good.
The problem of the user in the thread could be related by this Hibernate bug:
But this is a Hibernate bug, not an OpenXava one. When we'll upgrade the Hibernate version this bug will be solved. In the meantime the DB2 users can user JDBCTabProvider if they face performance problems.
Log in to post a comment.