[
https://issues.apache.org/jira/browse/JCR-1337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12561664#action_12561664
]
Marcel Reutegger commented on JCR-1337:
---------------------------------------
I already had those changes in my checkout ;)
Populating the cache is quite fast. On my machine I'm able to initialize the
cache at a rate of 180k nodes a second. But you are right the tough work still
is to resolve DocIds that point to other segments. I'd argue that those DocIds
are only a fraction, unless you have an application that heavily modifies
existing content.
> Optimize first execution queries for DescendantSelfAxisWeight/ChildAxisQuery
> ----------------------------------------------------------------------------
>
> Key: JCR-1337
> URL: https://issues.apache.org/jira/browse/JCR-1337
> Project: Jackrabbit
> Issue Type: Improvement
> Components: query
> Affects Versions: 1.4
> Reporter: Ard Schrijvers
> Fix For: 2.0
>
> Attachments: JCR-1337.patch
>
>
> The first execution of a query involving
> DescendantSelfAxisWeight/ChildAxisQuery is slow. Consecutive queries are
> faster because the hierarchy is cached
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
