[jira] Resolved: (JCR-1324) strange performance issue when using XPath query

["Christoph Kiehl (JIRA)" <ji...@apache.org>]

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

Christoph Kiehl resolved JCR-1324.
----------------------------------

    Resolution: Duplicate
      Assignee: Christoph Kiehl

Thanks for reporting but this is a knows issue and a duplicate of JCR-1196. Please ask on the mailing list before creating issues.

> strange performance issue when using XPath query
> ------------------------------------------------
>
>                 Key: JCR-1324
>                 URL: https://issues.apache.org/jira/browse/JCR-1324
>             Project: Jackrabbit
>          Issue Type: Bug
>          Components: query
>    Affects Versions: 1.4
>         Environment: Java 6, Linux
>            Reporter: Martin Zdila
>            Assignee: Christoph Kiehl
>
> I have following structure in my repository:
> jcr:root
>         gfr:devices
>                 gfr:device
>                         gfr:capabilityMap
> There are cca 4000 gfr:device nodes. Each gfr:device has only one gfr:capabilityMap. Each gfr:capabilityMap has average 20 properties.
> Here are some interesting results:
> 1.
> ((QueryImpl) query).setLimit(30);
> ((QueryImpl) query).setOffset(anyLimit);
> 1.1
> executing query //gfr:capabilityMap and fetching nodes takes cca 20-80ms
> 1.2
> executing query /jcr:root/gfr:devices/gfr:device/gfr:capabilityMap and fetching nodes takes cca 2000ms
> Why does this take longer time if the only difference is more specific path? I would expect even shorter time of execution and not this.
> 2.
> now without proprietary limit/offset
> 2.1
> //gfr:capabilityMap
> cca 150-200ms
> 2.2
> /jcr:root/gfr:devices/gfr:device/gfr:capabilityMap
> cca 14000ms!!!

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