jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joel Richard (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OAK-2679) Query engine: cache execution plans
Date Mon, 03 Aug 2015 06:55:05 GMT

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

Joel Richard commented on OAK-2679:

Should the execution plan for some query index type change more often, we could also add a
getCacheStrategy method to the QueryIndex interface which allows to control whether the execution
plan can be cached at all and if so for how long/until when.

> 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.5
>         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

View raw message