jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Serge Huber <shub...@jahia.com>
Subject Re: AW: jcr-sql2 queries "with or without" where-clause :-(
Date Fri, 19 Nov 2010 07:25:24 GMT

Hello Clemens, 

Yes that is similar to what I am seeing here. I have commented on the ticket https://issues.apache.org/jira/browse/JCR-2715
that we don't seem to be going through Jukka's new optimized code for simple queries that
don't use joins, which is a shame.

What happens if you use SQL-1 instead of SQL-2 for your queries (just as a basis of comparison
?)

Best regards,
  Serge Huber.

On 18 nov. 2010, at 18:10, Clemens Wyss wrote:

> addendum:
>> select * from [task] where @employeeinchargeid = 3
> returns after 90s to 120s
> 
> -----Urspr√ľngliche Nachricht-----
> Von: Clemens Wyss [mailto:clemensdev@mysign.ch] 
> Gesendet: Donnerstag, 18. November 2010 17:56
> An: dev@jackrabbit.apache.org
> Betreff: jcr-sql2 queries "with or without" where-clause :-(
> 
> I know that jcr-sql2 is "in progress". 
> Still I would like to know if my oberservations are at all possible:
> 
> I have approx. 76'000 [task]-nodes in my repo.
> 
>> select * from [task]
> takes approx. 870ms, :-)
> 
>> select * from [task] order by [jcr:score]
> takes btw. 2s and 5s (still somehow "acceptable")
> 
>> select * from [task] where employeeinchargeid = 3
> Seems to be neverending... I stopped my test after 10minutes! 
> employeeinchargeid is a simple int-property. 
> The xpath-pendant only takes 311ms, but xpath is deprecated.
> 
> Regards
> Clemens


Mime
View raw message