Showing results for 
Show  only  | Search instead for 
Did you mean: 

This product reached the end of support date on March 31, 2021.

Hibernate QueryImpl list method Performance Problem


For our report UI we query the sessions object and list it in the screen. To query the data we use Hibernate and a Generic Dao implementation. Before use Dynatrace we always blame database about this query but after start to use DynaTrace it shows us that the bottleneck is in the code at QueryImpl.list method. We have really bad performance both Prod and Dev, The total count records are about 2M in PROD and it takes 75 seconds(yes more than 1 minute 😞 ) Below screenshots show the Dynatrace Screenshots which show us problem is in Hibernate QueryImpl list method. I checked the application in DEV environment with 500K records and it takes 30 seconds in DEV too and same methods takes the 28 seconds at this query. I track the application get heap dump and analyze in dynatrace andjvisualvm. Also check thread dumps both at samurai and dyntarace but can not find any locked Thread or a lot of special class instance. I share dynatrace pure paths screenshots and our method call which use Spring @Transactional annotation.

@Target({ ElementType.METHOD, ElementType.TYPE })
@Transactional(readOnly = true)
public @interface ReadOnly {


public SearchResult<Session> getReport(ISearch search) {
return sessionDao.searchAndCount(search);

public <RT> SearchResult<RT> searchAndCount(ISearch search) {
if (search == null) {
SearchResult<RT> result = new SearchResult<RT>();
result.setResult((List<RT>) getAll());
return result;
return searchAndCount(persistentClass, search);

I spend 2-3 days to invesigate this problem and i really want to learn the reason. I checked the below questions but they are not present a solution

EDIT: I query 50 records form a 2M table, i use pagination approach and in purePaths i mentioned that it takes 2.5 seconds in database but it spends 75 seconds in memory QueryImpl list method. So I already query 50 records from 2M table which has index in date fields. @Andreas Grabner


Dynatrace Guru
Dynatrace Guru


So you said you read the hibernate blog articles that are referenced in one of the postings you mentioned here. I think the question is whether your code really needs to pull in 2M of rows? The list method is that slow because it has to process all the results that you are bringing back to Hibernate.

So: do you really need all 2M rows? Or do you just need a small subset that you need to display? If it is a small subset you need to make sure to define proper query filter parameters so that Hibernate doesnt need to query all 2M rows but just a smaller subset


Andreas thanks for your answer, i addressed the problem according to your suggesstions and SO help, I want to refer to my question and answer at SO.