[
https://issues.apache.org/jira/browse/GEODE-7756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17036143#comment-17036143
]
ASF subversion and git services commented on GEODE-7756:
--------------------------------------------------------
Commit 5dd7a8420bbe43657abc82e5b8d073eb01b51d8d in geode's branch
refs/heads/develop from Juan José Ramos
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=5dd7a84 ]
GEODE-7756: Do not use authorization cache for CQs (#4677)
CQs are executed on individual entries whenever an event is triggered
for them and the execution context is always cleared before the actual
evaluation, thus using an internal cache to keep already authorized
methods is useless (will always be a cache miss and the computation
required just adds overhead).
- Fixed the CQ creation to always set the 'cqQueryContext' flag.
- Modified the query engine to avoid using the internal cache for
already authorized methods when the context belongs to a CQ.
- Avoid the creation and concatenation of unnecessary Strings, using
the Method class directly instead.
> Performance Degradation on Clusters with CQs Introduced in GEODE-6989
> ---------------------------------------------------------------------
>
> Key: GEODE-7756
> URL: https://issues.apache.org/jira/browse/GEODE-7756
> Project: Geode
> Issue Type: Bug
> Components: cq, querying
> Affects Versions: 1.12.0
> Reporter: Juan Ramos
> Assignee: Juan Ramos
> Priority: Major
> Labels: GeodeCommons
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> On clusters with running {{CQs}}, a performance degradation was introduced by
> GEODE-6989 for regular cache operations.
> Every time an entry is updated on the cache, Geode internally (and
> synchronously) executes the registered {{CQs}} on the event entry to
> determine whether the subscribed clients should be notified or not. Due to
> the changes introduced through GEODE-6989, these regular cache operations now
> takes longer than expected (build internal cache key, check internal cache,
> and subsequent put if needed), reducing the throughput ~ %10.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
