[
https://issues.apache.org/jira/browse/DERBY-2327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Knut Anders Hatlen updated DERBY-2327:
--------------------------------------
Attachment: derby-2327-2a.stat
derby-2327-2a.diff
Attaching a new refactoring patch (2a). The patch moves all the methods from
SinglePool to a new abstract class called AbstractPool. AbstractPool is now the
super-class of SinglePool. The only code left in SinglePool is the creation of
the LockSet instance. The purpose of the patch is to make it easier to create a
new LockFactory class which is identical to SinglePool except that it uses
another LockSet implementation.
To apply the patch, first issue this command:
svn cp java/engine/org/apache/derby/impl/services/locks/SinglePool.java
java/engine/org/apache/derby/impl/services/locks/AbstractPool.java
All the tests passed on Solaris 10, Sun Java SE 6.
> 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
> Assigned To: Knut Anders Hatlen
> Priority: Minor
> Attachments: ConcurrentHashMap.diff, derby-2327-1a.diff,
> derby-2327-1a.stat, derby-2327-2a.diff, derby-2327-2a.stat
>
>
> 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.
