[
https://issues.apache.org/jira/browse/JCR-2715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12965248#action_12965248
]
Clemens Wyss commented on JCR-2715:
-----------------------------------
I see big improvements too :-) thanks!
BUT I have some real world examples where a simple sql2 queries perform very
bad compared to their sql1 pendants. The query .
SQL1:
select * from project order by jcr:score
returns 1'126 nodes and takes 84ms :-)
SQL2:
select * from [project] order by [jcr:score]
returns 1'126 nodes and takes 600ms , absolutely seen still ok, but compared to
the sql1 execution time
SQL1:
select * from task order by jcr:score
returns 76'281 nodes/rows and takes ~1.5s :-)
SQL2:
select * from [task] order by [jcr:score]
returns 76'281 nodes/rows and takes, fasten your seat belt, ~95s (!) :-(
My test where performed with the latest-greatest JR sources (2.3 SNAPSHOT)
> Improved join query performance
> -------------------------------
>
> Key: JCR-2715
> URL: https://issues.apache.org/jira/browse/JCR-2715
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
> Components: jackrabbit-core, query
> Reporter: Jukka Zitting
> Assignee: Jukka Zitting
> Fix For: 2.2.0
>
> Attachments: SQL2SearchTest.png, ThreeWayJoinTest.png,
> TwoWayJoinTest.png
>
>
> Our current implementation of SQL2 join queries does not perform very well on
> pretty much any non-trivial data set.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
