openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Abe White (JIRA)" <>
Subject [jira] Commented: (OPENJPA-138) More performance improvements for OpenJPA (lib and kernel)
Date Fri, 09 Feb 2007 16:26:05 GMT


Abe White commented on OPENJPA-138:

o Cache the TransactionManager in JNDIManagedRuntime 

o Cache the Class instances for Configurations.newInstance() 

o Cache the Type hashcodes for OpenJPAId.hashcode() 
Already being done as far as I can tell, unless you mean a static Class->hashcode map,
in which case -1.  

o Cache the Type's ClassLoader instances in ObjectValue.newInstance() 
I have a hard time believing that Class.getClassLoader() for the few things that we dynamically
create more than once via ObjectValues is a significant performance problem.  

o Cache the assignable "from" types and associated value "to" types in FetchConfigurationImpl.isAssignable
Again, I have a hard time believing this is significant.  What JVM is this that methods on
Class seem to be so ridiculously slow, to the point that you want to create and maintain Maps
of Maps to work around it?
o Clean up the close/IllegalStateException processing in AbstractBrokerFactory and BrokerImpl
(gate with TRACE)
o Cache the assignable "from" types and associated value "to" types in BrokerImpl.newObjectId()
Same comments as for FetchConfigurationImpl.isAssignable.

o Cache the brokers being created along with appropriate cleanup and reopen processing in
AbstractBrokerFactory (and BrokerImpl) 

> More performance improvements for OpenJPA (lib and kernel)
> ----------------------------------------------------------
>                 Key: OPENJPA-138
>                 URL:
>             Project: OpenJPA
>          Issue Type: Sub-task
>          Components: kernel, lib
>            Reporter: Kevin Sutter
>         Assigned To: Kevin Sutter
> As we continue pushing OpenJPA though its paces, we're finding a few additional tweaks
that help with the performance throughput.  This Issue will be used to track this next set
of improvements.  I'll document more detail as we determine the correct fixes.  Several of
the changes relate to caching of objects in a hashmap instead of re-creating the objects every
time we call some of these methods.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message