[
https://issues.apache.org/jira/browse/GEODE-6694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16824135#comment-16824135
]
ASF subversion and git services commented on GEODE-6694:
--------------------------------------------------------
Commit d746ec40ff4e2bf244d7b2474859f966b04d4e50 in geode's branch
refs/heads/develop from Jacob Barrett
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=d746ec4 ]
GEODE-6694: Use volatile access to read current state of BucketAdvisor
Since that value can change immediately after we exit these methods,
unless we already have the monitor, we can safely read the current value
with the same staleness guarantee when exiting the method. Lock still
acquired for composite checks and updating the value.
> Remove lock contention on BucketAdvisor.isHosting()
> ---------------------------------------------------
>
> Key: GEODE-6694
> URL: https://issues.apache.org/jira/browse/GEODE-6694
> Project: Geode
> Issue Type: Improvement
> Reporter: Jacob S. Barrett
> Assignee: Jacob S. Barrett
> Priority: Major
> Labels: performance
> Time Spent: 20m
> Remaining Estimate: 0h
>
> BucketAdvisor.isHosting takes lock to read and compare a value that could be
> volatile. Under heavy load, like server get operations, this can cause
> measurable contention.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
