You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "Michael Dürig (JIRA)" <ji...@apache.org> on 2014/08/27 12:19:58 UTC
[jira] [Commented] (OAK-2056) Optimize orderings by date fields
[ https://issues.apache.org/jira/browse/OAK-2056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14112111#comment-14112111 ]
Michael Dürig commented on OAK-2056:
------------------------------------
bq. Is there any reason why dates are using GenericPropertyState which keeps internally date as string ?
OAK-1111
> Optimize orderings by date fields
> ---------------------------------
>
> Key: OAK-2056
> URL: https://issues.apache.org/jira/browse/OAK-2056
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: query
> Affects Versions: 1.0.4
> Reporter: Przemo Pakulski
> Labels: performance
>
> Sorting by date fields is very slow in oak, especially if result set size is large.
> I'm running the following JCR-SQL2 query
> {code}
> SELECT * FROM [cq:PageContent] AS [c] WHERE ISDESCENDANTNODE('/content')
> {code}
> which returns 3270 results on my oak repo.
> {noformat}
> Query execution times are as below
> ---------------------------------------
> No order clause | 0,147 sec
> ORDER BY [jcr:title] | 1,203 sec
> ORDER BY [jcr:createdBy] | 1,018 sec
> ORDER BY [jcr:created] | 25,229 sec
> {noformat}
> Ordering by date field adds extra 24 seconds overhead.
--
This message was sent by Atlassian JIRA
(v6.2#6252)