Hi AmitS , maybe that’s relevant but it doesn’t ring a bell. Would you be able to trace which classes?

I see from the stacks you provided that these are triggered by Spring while creating a proxy for the EntityManager. I suppose this might relate with the fact that we merged Session and EntityManager, so that object implements several more interfaces - perhaps that utility method in Spring could be optimisize.

Maybe the Spring team already optimised this? You mentioned you upgraded Hibernate ORM only : it might be a good idea to check if updating Spring to a version which is actually meant for this version of ORM would solve your issue?

Also: we just released Hibernate ORM 5.4.4.Final ; it has several performance optimisations so it might be worth for you testing - however I don’t think it includes anything relating to your specific profile data.