Hypersistence Optimizer allows you to get the most out of JPA and Hibernate. By scanning your application configuration and mappings, Hypersistence Optimizer can tell you what changes you need to do to speed up your data access layer.
I recently got started with Hypersistence Optimizer. I've followed your posts for a long time and really appreciate the hard work on this tool. When I run my instrumented tests I can see an event it has collected:
CRITICAL - SecondaryQueryEntityFetchingEvent - The [class $CLASS] entity with the identifier value of [$ID] has been loaded using a secondary query instead of being fetched using a JOIN FETCH clause. For more info about this event, check out this User Guide link - https://vladmihalcea.com/hypersistence-optimizer/docs/user-guide/#SecondaryQueryEntityFetchingEvent
Hi Vlad,
I recently got started with Hypersistence Optimizer. I've followed your posts for a long time and really appreciate the hard work on this tool. When I run my instrumented tests I can see an event it has collected:
CRITICAL - SecondaryQueryEntityFetchingEvent - The [class $CLASS] entity with the identifier value of [$ID] has been loaded using a secondary query instead of being fetched using a JOIN FETCH clause. For more info about this event, check out this User Guide link - https://vladmihalcea.com/hypersistence-optimizer/docs/user-guide/#SecondaryQueryEntityFetchingEvent
As far as I can tell, https://vladmihalcea.com/hypersistence-optimizer/docs/user-guide/#SecondaryQueryEntityFetchingEvent is a dead link. Is there a different event I should be looking at for this?
Cheers
Alex