Hi,

I'm trying to track down a performance problem and profiling has led me to wonder what Cascade.cascade and CascadeAction.noCascade are doing. The application spends most of its time in these two methods. The application is only performing reads, so this seems counter intuitive to me.

I'm using hibernate 5.2.3 if that matters.

Thanks for any help.

Reid

For read-only transactions, you need to fetch read-only entities so that the dirty checking mechanism does not fire.

For example, if the current Session only needs to fetch read-only entities, yu can set this flag:



or use a query hint:

Thank you so much! I'll give it a try.

Edit: Yes, that really helped. Making the transaction read only improved the query time by over 20x!