db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-4478) Use AtomicLong for XactFactory.tranId
Date Mon, 15 Jul 2013 09:54:49 GMT

    [ https://issues.apache.org/jira/browse/DERBY-4478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13708351#comment-13708351
] 

ASF subversion and git services commented on DERBY-4478:
--------------------------------------------------------

Commit 1503157 from [~knutanders] in branch 'code/trunk'
[ https://svn.apache.org/r1503157 ]

DERBY-4478: Use AtomicLong for XactFactory.tranId
                
> 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
>         Attachments: d4478-1a.diff
>
>
> 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

Mime
View raw message