You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openjpa.apache.org by "Rick Curtis (JIRA)" <ji...@apache.org> on 2012/11/06 16:30:13 UTC
[jira] [Updated] (OPENJPA-2292) Reduce object allocations
[ https://issues.apache.org/jira/browse/OPENJPA-2292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rick Curtis updated OPENJPA-2292:
---------------------------------
Description:
While doing some performance analysis we have found that we can reduce object allocations a number of places in the code base.
* In JDBCStoreManager we can create a simple pool(list) of CancelPreparedStatement/CancelStatement.
* BrokerImpl.initializeOperatingSet, use a java.util.IdentityHashMap rather than org.apache.commons.collections.map.IdentityMap.IdentityMap.
was:While doing some performance analysis we have found that we can reduce object allocations in JDBCStoreManager by creating a simple pool(list) of CancelPreparedStatement/CancelStatement.
Summary: Reduce object allocations (was: Reduce object allocations in JDBCStoreManager)
> Reduce object allocations
> -------------------------
>
> Key: OPENJPA-2292
> URL: https://issues.apache.org/jira/browse/OPENJPA-2292
> Project: OpenJPA
> Issue Type: Improvement
> Components: jdbc, performance
> Affects Versions: 2.3.0, 2.2.1, 2.2.1.x
> Reporter: Rick Curtis
> Assignee: Rick Curtis
> Fix For: 2.3.0, 2.2.1, 2.2.1.x
>
>
> While doing some performance analysis we have found that we can reduce object allocations a number of places in the code base.
> * In JDBCStoreManager we can create a simple pool(list) of CancelPreparedStatement/CancelStatement.
> * BrokerImpl.initializeOperatingSet, use a java.util.IdentityHashMap rather than org.apache.commons.collections.map.IdentityMap.IdentityMap.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira