[
https://issues.apache.org/jira/browse/DERBY-2327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12489042
]
Kristian Waagan commented on DERBY-2327:
----------------------------------------
I've been using this patch in various loads, and have not seen any problems
because of it.
Note that I have not reviewed the patch, so it would be nice if anyone took a
look at it.
But my experience from using the patch is that it works without problems and I
do see performance improvements. The increase varies quite a lot depending on
the type of load.
+1 for commit, with a wish for code review first :)
> 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: 2cpu-join.png, 2cpu-select.png, 8cpu-join.png,
> 8cpu-select.png, ConcurrentHashMap.diff, derby-2327-1a.diff,
> derby-2327-1a.stat, derby-2327-2a.diff, derby-2327-2a.stat,
> derby-2327-3a.diff, derby-2327-4a.diff, derby-2327-4a.stat, niagara-join.png,
> niagara-select.png
>
>
> 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.
