[
https://issues.apache.org/jira/browse/JCR-1337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12561699#action_12561699
]
Ard Schrijvers commented on JCR-1337:
-------------------------------------
>the only difference between DocId.create(String) and DocId.create(int) is
>parsing the uuid string. I'm not sure how significant that is. It is certainly
>>slower than the int variant, but it's much less called.
Ooow, that is certainly not what i meant (i am certainly not pushing on the
difference between parsing a uuid string and just an int!! ): I thought that
for building the hierarchy cache in your pre-warming the
getDocumentNumber(MultiIndexReader reader) in DocId.UUIDDocId was also
executed. I scanned your patch and must have interpreted it incorrectly (also
because I assumed it would do some parts regarding looking up parents). I
assumed it would call the 'expensive' getDocumentNumber(MultiIndexReader
reader).... I am a little puzzled ATM how it works, and what is pre-warmed. I
just need to test your patch because I am clearly off track. Disregard my
remarks, I'll try to find some time to take a better look. Sry for any confusion
> 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, 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.
