[
https://issues.apache.org/jira/browse/OAK-2056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14242448#comment-14242448
]
Przemo Pakulski commented on OAK-2056:
--------------------------------------
Any plans to fix it ?
If we have to store dates as strings, it would be good to limit number of
conversions at least which are quite expensive.
I've take a look, but cannot see good place to change it.
> Optimize orderings by date fields
> ---------------------------------
>
> Key: OAK-2056
> URL: https://issues.apache.org/jira/browse/OAK-2056
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: query
> Affects Versions: 1.0.4, 1.0.8
> 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.3.4#6332)
