openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Curtis (JIRA)" <j...@apache.org>
Subject [jira] Commented: (OPENJPA-1545) Add new Detach processing
Date Tue, 16 Mar 2010 17:02:27 GMT

    [ https://issues.apache.org/jira/browse/OPENJPA-1545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12845998#action_12845998
] 

Rick Curtis commented on OPENJPA-1545:
--------------------------------------

@Pinaki - Per the doc that was committed in 918643: "...It is highly recommended that all
Entities have a @Version field when using this property." 

On second thought, I probably need to make having a version field a requirement. The version
field is used when we calculate whether or not a given Entity is detached when there is no
state manager present. 

@Patrick - Sorry I missed your update before. From a high level this change can be described
as, "OpenJPA give me my POJOs back." We found that the loaded setting does a fair amount of
work validating that fields that should be loaded actually are. I short cut that entire path
and completed the minimum amount of work to disassociate an Entity from the PersistenceContext.


http://n2.nabble.com/Extreme-performance-problems-with-OpenJPA-commit-td4497009.html

> Add new Detach processing
> -------------------------
>
>                 Key: OPENJPA-1545
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-1545
>             Project: OpenJPA
>          Issue Type: Improvement
>          Components: performance
>    Affects Versions: 2.0.0-beta2
>            Reporter: Rick Curtis
>            Assignee: Rick Curtis
>             Fix For: 2.0.0
>
>         Attachments: OPENJPA-1545.patch
>
>
> There have been a number of mailing list posts where the net of the post is that someone
doesn't want OpenJPA to detach their Entities because after the commit happens, then are all
going to be gc'd. All of the detach processing ends up being a waste.  I also observed this
same behavior when running some performance tests.
> With this JIRA I'm going to add a new openjpa.DetachState configuration option which
will enable a new, super fast, minimalistic detach approach. This change is targeted at detach
processing that happens due to an AutoDetach. Explicit detaches(ie: em.detach(..) ) will work
as they always have before.

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


Mime
View raw message