jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcel Reutegger (JIRA)" <j...@apache.org>
Subject [jira] Updated: (JCR-1365) Query path constraints like foo//*/bar do not scale
Date Tue, 12 Feb 2008 17:07:14 GMT

     [ https://issues.apache.org/jira/browse/JCR-1365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Marcel Reutegger updated JCR-1365:

    Attachment: Book1_25575_image001.png

The chart shows the time to run the 20 most expensive queries executed by AxisQueryTest. Please
note that NUM_LEVELS was set to 4 and NODES_PER_LEVEL was set to 10. This results in about
11k test nodes. CHECK_RESULTS was disabled. Furthermore respectDocumentOrder was set to false!

The vertical axis is logarithmic and shows the time in milliseconds.

- first series: jackrabbit-core when this issue was reported
- second series: with improvements implemented so far
- third series: same as second series but cacheSize for DocNumberCache was set to 20'000

> Query path constraints like foo//*/bar do not scale
> ---------------------------------------------------
>                 Key: JCR-1365
>                 URL: https://issues.apache.org/jira/browse/JCR-1365
>             Project: Jackrabbit
>          Issue Type: Improvement
>          Components: jackrabbit-core
>            Reporter: Marcel Reutegger
>            Priority: Minor
>         Attachments: Book1_25575_image001.png
> To resolve the * step the LuceneQueryBuilder currently creates a MatchAllQuery and checks
every node for a foo ancestor. Instead, it should search for bar nodes and check for foo ancestors
with at least one arbitrary hierarchy level in between.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message