[ 
https://issues.apache.org/jira/browse/GEODE-2141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15704812#comment-15704812
 ] 

ASF GitHub Bot commented on GEODE-2141:
---------------------------------------

GitHub user davinash opened a pull request:

    https://github.com/apache/incubator-geode/pull/299

    [ GEODE-2141 ] #comment Fix Issue #2141

    Replaced List with ConcurrentHashSet

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/davinash/incubator-geode feature/GEODE-2141

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/incubator-geode/pull/299.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #299
    
----
commit e4da4c43dc691e59d34640e95c5d63a5a1b0ea1c
Author: adongre <[email protected]>
Date:   2016-11-27T14:11:48Z

    GEODE-2141: Replace use of List with ConcurrentHashSet for storing various 
stats and listener.
    Moved methods stopNotifier_IfEnabledAndRunning and 
startNotifier_IfEnabledAndNotRunning in synchronized
    block.

----


> StatisticsMonitor and StatMonitorHandler should use ConcurrentHashSet to 
> store monitors, listeners and statisticIds
> -------------------------------------------------------------------------------------------------------------------
>
>                 Key: GEODE-2141
>                 URL: https://issues.apache.org/jira/browse/GEODE-2141
>             Project: Geode
>          Issue Type: Improvement
>            Reporter: Avinash Dongre
>            Assignee: Avinash Dongre
>
> In StatisticsMonitor and StatMonitorHandler List is used to store monitors, 
> listeners and statisticIds.
> We should be using ConcurrentHashSet for performance Reason.
> In my local testing  When I replace the List to 
> com.gemstone.gemfire.internal.concurrent.
> ConcurrentHashSet
> I see significant improvement in creating large number of region creation.
> ( from ~7hrs to ~26 minutes)
> More details about the same is on dev list.
> Refer : http://markmail.org/message/o7td3fczylx4uaet



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to