You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@geode.apache.org by "Avinash Dongre (JIRA)" <ji...@apache.org> on 2016/11/25 08:41:58 UTC

[jira] [Created] (GEODE-2141) StatisticsMonitor and StatMonitorHandler should use ConcurrentHashSet to store monitors, listeners and statisticIds

Avinash Dongre created GEODE-2141:
-------------------------------------

             Summary: 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


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)