jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Marth (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OAK-2679) Query engine: cache execution plans
Date Thu, 30 Jul 2015 14:58:07 GMT

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

Michael Marth commented on OAK-2679:
------------------------------------

[~joelrich], impressive numbers.
[~tmueller], I was still wondering about what would be the best cache flush strategy: would
it be correct to assume that the query plans for a given query rarely change? (e.g. that would
happen only if the number of items grows significantly for one index compared to another).
If so, we could really just use a large TTL for cache flushes. WDYT?

> 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
(v6.3.4#6332)

Mime
View raw message