[
https://issues.apache.org/jira/browse/GEODE-6577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16807097#comment-16807097
]
ASF subversion and git services commented on GEODE-6577:
--------------------------------------------------------
Commit ed8b17497b091e7eba55f45ae5a25632a7703389 in geode's branch
refs/heads/develop from Helena Bales
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=ed8b174 ]
GEODE-6577: performance gain by removing lazy init (#3378)
There was lock contention for checking if the clientMetadataService
needed to be initialized. The object is not expensive to construct, so
the initialization has been moved the GemFireCacheImpl's constructor,
allowing the lock object to be removed completely.
> Performance Improvement: init object in constructor
> ---------------------------------------------------
>
> Key: GEODE-6577
> URL: https://issues.apache.org/jira/browse/GEODE-6577
> Project: Geode
> Issue Type: Improvement
> Reporter: Helena Bales
> Assignee: Helena Bales
> Priority: Major
> Labels: performance-benchmark
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> Initialize inexpensive object in the constructor for GemfireCacheImpl instead
> of in a hot code path, while holding a lock. This will result in a noticeable
> performance gain.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
