[jira] [Commented] (OAK-2679) Query engine: cache execution plans

["Thomas Mueller (JIRA)" <ji...@apache.org>]

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

Thomas Mueller commented on OAK-2679:
-------------------------------------

I will change the minimum costs per index type slightly:
* 0.0 for uuid
* 0.0 for traversal
* 1.0 for reference
* 2.0 for property
* 2.0 for nodetype
* 2.1 for lucene property
* 2.2 for lucene (old)
* 2.3 for solr
* 3.0 for ordered (deprecated)

> 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.7
>
>         Attachments: 0001-OAK-2679-Reduce-execution-plan-overhead_0.2.patch, 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)