[
https://issues.apache.org/jira/browse/OAK-2679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14647632#comment-14647632
]
Joel Richard edited comment on OAK-2679 at 8/3/15 6:48 AM:
-----------------------------------------------------------
[~mmarth], here are a few numbers about the time which is lost at the moment
with finding the best execution plan:
Static files: 21% of the request (query time is 22%)
Page 1: 9.5% of the request (query time is 10.5%)
Page 2: 5% of the request (query time is 5.5%)
Login: 65% of the repository login time
was (Author: joelrich):
[~mmarth], here are a few numbers about the time which is lost at the moment
with finding the best execution plan:
Static files: 21% of the request (query time is 22%)
Page 1: 9.5% of the request (query time is 10.5%)
Page 2: 5% of the request (query time is 5.5%)
Login: 65% of the session login time
> 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)
