db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-3092) Use java.util.concurrent in TransactionTable to improve scalability
Date Wed, 10 Feb 2010 12:46:39 GMT

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

Knut Anders Hatlen commented on DERBY-3092:

Thanks for looking at the patch, Kristian!
Committed revision 908473.

I'll leave the issue open until I've had a chance to run the test where Dyre saw some unexplained
behaviour with the concept patch.

> 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:
>            Reporter: Dyre Tjeldvoll
>            Assignee: Knut Anders Hatlen
>         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.

View raw message