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 "Daniel John Debrunner (JIRA)" <ji...@apache.org> on 2007/02/13 16:22:05 UTC

[jira] Commented: (DERBY-2327) Reduce monitor contention in LockSet

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

Daniel John Debrunner commented on DERBY-2327:
----------------------------------------------

Does it make sense to use java.util.concurrent.ConcurrentHashMap and have two implementation of the lock factory.
Ie. use Java's existing mechanisms to solve this problem rather than re-inventing stuff?
Obviously the benefit would only be seeon on JDK 5.0 or later but I don't think that's a problem.

> Reduce monitor contention in LockSet
> ------------------------------------
>
>                 Key: DERBY-2327
>                 URL: https://issues.apache.org/jira/browse/DERBY-2327
>             Project: Derby
>          Issue Type: Sub-task
>          Components: Performance, Services
>    Affects Versions: 10.3.0.0
>            Reporter: Knut Anders Hatlen
>            Priority: Minor
>
> When multiple threads enter the lock manager, only one can access the hash table in LockSet. To improve scalability on multiple CPUs, it should be possible to have more than one thread accessing the lock table at the same time.

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