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 "Rishabh Maurya (JIRA)" <ji...@apache.org> on 2014/09/11 15:03:34 UTC
[jira] [Updated] (OAK-2092) benchmark for multiple lucene property
index
[ https://issues.apache.org/jira/browse/OAK-2092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rishabh Maurya updated OAK-2092:
--------------------------------
Attachment: OAK-2092.patch
h4. MultiLucenePropertyIndexSearchTest
* -DpreAddedNodes number of nodes to be added before test with some indexed property
* -DmatchingResults number of matching results on each search (optional)
* -DpersistencePath lucene index persistence path (optional)
command -
{code}
java -jar -DpreAddedNodes=1000 -DmatchingResults=2 -DpersistencePath=/home/maurya/Desktop/benchmark/index oak-run-1.1-SNAPSHOT.jar benchmark MultiLucenePropertyIndexSearchTest Oak-Tar
{code}
h4. StandardPropertyIndexSearchTest
QueryEngine property index will be used for comparison on similar setup
command -
{code}
java -jar -DpreAddedNodes=1000 -DmatchingResults=2 oak-run-1.1-SNAPSHOT.jar benchmark StandardPropertyIndexSearchTest Oak-Tar
{code}
> benchmark for multiple lucene property index
> --------------------------------------------
>
> Key: OAK-2092
> URL: https://issues.apache.org/jira/browse/OAK-2092
> Project: Jackrabbit Oak
> Issue Type: Sub-task
> Components: bench, oak-lucene
> Reporter: Rishabh Maurya
> Assignee: Chetan Mehrotra
> Priority: Minor
> Fix For: 1.1
>
> Attachments: OAK-2092.patch
>
>
> Benchmark test for multiple lucene property index with a configurations like -
> Number of nodes, number of matching results etc.
> Test should run property matching queries using lucene index.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)