You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Dan Smith (JIRA)" <ji...@apache.org> on 2016/10/25 16:41:58 UTC
[jira] [Updated] (GEODE-1669) Performance issue with Interest
registration with impact on client side event processing.
[ https://issues.apache.org/jira/browse/GEODE-1669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dan Smith updated GEODE-1669:
-----------------------------
Fix Version/s: (was: 2.0.0-incubating)
1.0.0-incubating.M3
> Performance issue with Interest registration with impact on client side event processing.
> -----------------------------------------------------------------------------------------
>
> Key: GEODE-1669
> URL: https://issues.apache.org/jira/browse/GEODE-1669
> Project: Geode
> Issue Type: Bug
> Components: client queues
> Reporter: Anilkumar Gingade
> Assignee: Anilkumar Gingade
> Fix For: 1.0.0-incubating.M3
>
>
> The client interests are managed in "FilterProfile" class on server side. These are maintained using the concurrent data structures CopyOnWriteHashSet and CopyOnWriteHashMap...
> When set of keys are registered from client, the keys are added to CopyOnWriteHashSet one by one (FilterProfile.registerClientInterestList()); Where a new HashSet is created each time when an entry is added, which could impact performance based on the number of keys registered.
> This will have implication on the client side event processing; as the event processing gets blocked when a interest registration is in progress by other thread.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)