[jira] Resolved: (DERBY-3092) Use java.util.concurrent in TransactionTable to improve scalability

["Knut Anders Hatlen (JIRA)" <ji...@apache.org>]

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

Knut Anders Hatlen resolved DERBY-3092.
---------------------------------------

    Fix Version/s: 10.6.0.0
       Resolution: Fixed

Thank you very much for running these tests, Kristian! No other problems related to this fix have been seen after the commit, as far as I'm aware, so I'm resolving the issue.

> Use java.util.concurrent in TransactionTable to improve scalability
> -------------------------------------------------------------------
>
>                 Key: DERBY-3092
>                 URL: https://issues.apache.org/jira/browse/DERBY-3092
>             Project: Derby
>          Issue Type: Improvement
>          Components: Store
>    Affects Versions: 10.3.1.4
>            Reporter: Dyre Tjeldvoll
>            Assignee: Knut Anders Hatlen
>             Fix For: 10.6.0.0
>
>         Attachments: derby-3092-1a-map.diff, derby-3092-1b-map.diff, derby-3092-2a-count.diff, derby-3092-3a-xa-visitor.diff, derby-3092-4a-more-visitors.diff, derby-3092-5a-dynamic-loading.diff, derby-3092-5a-dynamic-loading.stat, xact-concept.diff, xact-concept.png
>
>
> Running scalability tests with the client and buffer manager from DERBY-2911 shows that access to the TransactionTable.trans (a Hashtable) and XactFactory.tranId (a shared long) are the next major sources of contention. 

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