One quick update, I re-ran my 20 sequential query test using the query that
does not have a date in it.
//element(*,my:namespace)[...@property='value'] order by @datestart descending
The results for that test are:
1.5 = 16 seconds to run all 20 queries
1.6 = 7.9 seconds to run all 20 queries
So there is definitely something about the date field that is causing a
performance issue. I am using OCM if that makes a difference.
majohnst wrote:
>
> I am evaluating migrating from 1.5 to 1.6. I created several test cases
> that prove the query performance of 1.6 is the same or better than 1.5.
> That is until I add a date property into my query.
>
> In my tests, my base query is:
> //element(*,my:namespace)[...@property='value'] order by @datestart
> descending
>
> The time to run this query in 1.5 and 1.6 is:
> 1.5 = 1.5 seconds
> 1.6 = 1.5 seconds
>
> If I add a date property:
> //element(*,my:namespace)[...@property='value' and
> @datestart<=xs:dateTime('2009-09-24T11:53:23.293-05:00')] order by
> @datestart descending
>
> the results are:
> 1.5 = 1.5 seconds
> 1.6 = 3.5 seconds
>
> What changed in version 1.6 that would cause the date performance to
> degrade so much?
>
--
View this message in context:
http://www.nabble.com/Date-Property-Performance-in-1.6-tp25704607p25716507.html
Sent from the Jackrabbit - Users mailing list archive at Nabble.com.
