Sanne Grinovero ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiODdhNzNlMDZj... ) / Task ( https://hibernate.atlassian.net/browse/HHH-15566?atlOrigin=eyJpIjoiODdhNz... ) HHH-15566 ( https://hibernate.atlassian.net/browse/HHH-15566?atlOrigin=eyJpIjoiODdhNz... ) Improve efficiency of CallbackRegistryImpl ( https://hibernate.atlassian.net/browse/HHH-15566?atlOrigin=eyJpIjoiODdhNz... ) Issue Type: Task Assignee: Unassigned Created: 01/Oct/2022 10:20 AM Priority: Major Reporter: Sanne Grinovero ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) The various HashMap<Class,Callback[]> managed by CallbackRegistryImpl have been identified as having a disproportionate cost to efficiency, compared to other areas. It would seem worthwhile to explore some options, perhaps: * use a different data structure to maintain the mapping * store some very hot data within the EntityPersister And not limited to these ideas. This in particular shows as very hot in a benchmark performing many updates: {{Object java.util.HashMap.get(Object) 97 62.6 %}} {{ void org.hibernate.jpa.event.internal.CallbackRegistryImpl.postUpdate(Object) 24 15.5 %}} ( https://hibernate.atlassian.net/browse/HHH-15566#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-15566#add-comment?atlOrigin=ey... ) Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.... ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=Em... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100207- sha1:ee9e30a )