[
https://issues.apache.org/jira/browse/OAK-1806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14010853#comment-14010853
]
Amit Jain commented on OAK-1806:
--------------------------------
Execution times on an Amazon EC2 large instance with Tar for blob loads as below
||Test||Time ms (10000)||Time ms (60000)||Time ms(160000)||Time
ms(660000)||Time ms(1660000)||
|LastModifiedSearcher::Week|17|15|14|13|13|
|NodeTypeSearcher |7|11|27|30|58|
|LastModifiedSearcher::Mont|16|13|13|12|12|
|FormatSearcher |151|908|1895|1240|4852|
|LastModifiedSearcher::Year|15|13|12|12|12|
|LastModifiedSearcher::Day|21|28|35|17|35|
|LastModifiedSearcher::Hour|26|28|35|22|42|
|FullTextSearcher |16|99|45|57|228|
The {{FormatSearcher}} takes the most time and seems to scale linearly. On,
debugging it seems even when index is created on the 'format' field, the index
picked up is the NodeTypeIndex, because of multiple or clauses in the
condition. Not sure if this is the reason for the slowness of the query here.
The LastModifiedSearcher takes quite a less time on this instance.
> 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)
