openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Albert Lee (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (OPENJPA-2151) Improve the performance of StateManagerImpl.initialize
Date Tue, 09 Oct 2012 18:42:02 GMT

     [ https://issues.apache.org/jira/browse/OPENJPA-2151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Albert Lee closed OPENJPA-2151.
-------------------------------

    
> Improve the performance of StateManagerImpl.initialize 
> -------------------------------------------------------
>
>                 Key: OPENJPA-2151
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-2151
>             Project: OpenJPA
>          Issue Type: Improvement
>          Components: kernel
>    Affects Versions: 2.2.0, 2.3.0
>            Reporter: Rick Curtis
>            Assignee: Rick Curtis
>            Priority: Minor
>             Fix For: 2.3.0, 2.2.1
>
>         Attachments: openjpa-2151.patch
>
>
> While running some performance tests I found that StateManagerImpl.initialize could be
improved through caching some additional meta data. 
> I also found another improvement that could be added to the PCState.initialize(...) transition.
As far as I can tell, the PCState transition(s) do not have a concept of what state they are
coming from and in some instances we are doing work unnecessary work. For example, when finding
an Entity with an active transaction, we have all clean bitsets, but when we call PCleanState.initialize(...)
the state doesn't know that this is a 'fresh' instance and we don't need to touch the dirty
bitset. 

--
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

Mime
View raw message