You are viewing a plain text version of this content. The canonical link for it is here.

Posted to derby-dev@db.apache.org by "Knut Anders Hatlen (JIRA)" <ji...@apache.org> on 2013/07/12 12:21:48 UTC

[jira] [Assigned] (DERBY-4478) Use AtomicLong for XactFactory.tranId

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

Knut Anders Hatlen reassigned DERBY-4478:
-----------------------------------------

    Assignee: Knut Anders Hatlen
    
> Use AtomicLong for XactFactory.tranId
> -------------------------------------
>
>                 Key: DERBY-4478
>                 URL: https://issues.apache.org/jira/browse/DERBY-4478
>             Project: Derby
>          Issue Type: Improvement
>          Components: Store
>    Affects Versions: 10.6.1.0
>            Reporter: Knut Anders Hatlen
>            Assignee: Knut Anders Hatlen
>            Priority: Minor
>
> Dyre Tjeldvoll posted some results on DERBY-3092 that indicated that some types of load might cause contention on XactFactory.tranId (a shared long), and suggested that it was replaced with a java.util.concurrent.atomic.AtomicLong on the platforms that support java.util.concurrent.*.
> I'm splitting this issue out from DERBY-3092 so that the two possible improvements reported there can be addressed independently.

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