I have a question about criteria. In a webpage, I only need display first 20 rows. When we create a criteria for a class. Then we set first result and fetch size. Does the underlying JDBC fetchs all rows and criteria just iterator its and return the targeted rows. In this way, does JDBC result set consumes a lot of JVM memory?

Criteria criteria = sessionFactory.getCurrentSession().createCriteria(Application.class);
criteria.setFirstResult(11).setFetchSize(10).list();

According to my experience so far, criteria query with first/maxResults set is too slow!

Our construct for pagination:
1. create Hibernate Query object

2. derive a ScrollableResults object

3. scroll to first result and build paging *manually* (no kidding, it's the fastest way, we found)


Please notify me if you find out any more about this problem and performance regards.

Thanks.

if you use Spring JDBC template for pagination, it will work fast .. I implemented and tested . but I don't know why use Criteria... with hibernate that slow... if use hibernate native sql can be possible to have performance issue to be solved ?

any idea?

Thanks in advance