[
https://issues.apache.org/jira/browse/OAK-2679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14593091#comment-14593091
]
Joel Richard commented on OAK-2679:
-----------------------------------
[~mmarth], I would expect that the cache size stays quite stable. But maybe we
could limit the cache entries and once the threshold is reached remove the
least used execution plans?
> Query engine: cache execution plans
> -----------------------------------
>
> Key: OAK-2679
> URL: https://issues.apache.org/jira/browse/OAK-2679
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: core, query
> Reporter: Thomas Mueller
> Assignee: Thomas Mueller
> Labels: performance
> Fix For: 1.3.1, 1.2.4
>
> Attachments: OAK-2679.patch, executionplancache.patch
>
>
> If there are many indexes, preparing a query can take a long time, in
> relation to executing the query.
> The query execution plans can be cached. The cache should be invalidated if
> there are new indexes, or indexes are changed; a simple solution might be to
> use a timeout, and / or a manual cache clean via JMX or so.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
