[
https://issues.apache.org/jira/browse/JCR-1337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12561669#action_12561669
]
Ard Schrijvers commented on JCR-1337:
-------------------------------------
180k nodes a sec is really fast, but might also be in your test setup where
the parent ids are not scattered around over many different indexes. It might
get quite a bit slower then isn't? Even if 2 large indexes merge, the amount
of time needed for pre-warming is small compared to the time taken for merging
I suppose?
> I've added logging information to the CachingIndexReader, which now write the
> percentage of UUIDDocIds
This is nice info to monitor!
> 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, 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.
