[
https://issues.apache.org/jira/browse/OAK-1806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14004434#comment-14004434
]
Amit Jain commented on OAK-1806:
--------------------------------
The following execution times were recorded for different search tests
(Oak-Tar-FDS) for blob loads 10000, 35000, 85000.
||Test||Time ms (10000)||Time ms (35000)||Time ms(85000)||
|LastModifiedSearcher::Week|21|18|17|
|NodeTypeSearcher |25|53|92|
|LastModifiedSearcher::Mont|24|15|14|
|FormatSearcher |471|851|2123|
|LastModifiedSearcher::Year|22|18|23|
|LastModifiedSearcher::Day|32|27|31|
|LastModifiedSearcher::Hour|248|1473|3687|
|FullTextSearcher |39|46|46|
It looks like FormatSearcher and the LastModifiedSearcher:Hour execution times
scale linearly and > linear with the blob/node loads. The test was run with an
index on the 'format' property, but without an index on the 'jcr:lastModified'
property.
Will add an ordered index on the jcr:lastModified property to check if the
LastModifiedSearcher:Hour execution times improve.
Other tests seem fine at this load.
[~edivad] thoughts?
> Benchmark for blob upload and search longevity
> ----------------------------------------------
>
> Key: OAK-1806
> URL: https://issues.apache.org/jira/browse/OAK-1806
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: run
> Reporter: Amit Jain
> Labels: benchmark, test
> Attachments: OAK-1806-SDF.patch, OAK-1806-doc.patch, OAK-1806.patch
>
>
> Have a longevity test which incrementally increases the load by adding blobs
> and then running full text search to measure the execution times and the
> performance degradation for increased loads.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
