[
https://issues.apache.org/jira/browse/OAK-9180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17179688#comment-17179688
]
Andrei Dulceanu commented on OAK-9180:
--------------------------------------
[~smiroslav], how about renaming the two methods previously responsible with
locking/unlocking with something more relevant to their current purpose?
> Optimise synchronisation between threads when writing to 3rd level segment
> cache
> ---------------------------------------------------------------------------------
>
> Key: OAK-9180
> URL: https://issues.apache.org/jira/browse/OAK-9180
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Reporter: Miroslav Smiljanic
> Assignee: Andrei Dulceanu
> Priority: Minor
> Attachments: OAK-9180.patch
>
>
> Currently threads that are updating 3rd level segment cache, are obtaining
> lock on the instance of HashMap, before inserting segmentId.
> This can be optimised by using Set, obtained from
> ConcurrentHashMap.newKeySet().
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
