openjpa-dev mailing list archives

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


Kevin Sutter commented on OPENJPA-138:

To give everyone a heads up on the type of changes I plan to introduce via this Issue... 
Please comment if you see a problem with any of these approaches.  Our current OpenJPA test
bucket still passes, but that doesn't always mean that these are safe...

o  Cache the TransactionManager in JNDIManagedRuntime
o  Cache the Class instances for Configurations.newInstance()
o  Cache the Type hashcodes for OpenJPAId.hashcode()
o  Cache the Type's ClassLoader instances in ObjectValue.newInstance()
o  Cache the assignable "from" types and associated value "to" types in FetchConfigurationImpl.isAssignable
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()
o  Cache the brokers being created along with appropriate cleanup and reopen processing in
AbstractBrokerFactory (and BrokerImpl)

The details can be found with the SVN commit.  Hopefully, this gives enough of a flavor to
possibly raise any red flags...


> 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