[
https://issues.apache.org/jira/browse/OAK-1702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13965114#comment-13965114
]
Alex Parvulescu commented on OAK-1702:
--------------------------------------
+1 for [~teofili]'s patch. I also asked on the lucene list about this and it
looks there is no way around decompressing everything, which in our case
because of the fact that we are storing all text content in the index is a lot
[0].
Another thing we could do is to also implement a custom field visitor that
returns 'STOP' once it hit the path, and rearranging the path to be the first
field should also give it a small boost.
I could take care of that if Tommaso doesn't mind.
[0]
http://lucene.472066.n3.nabble.com/Performance-issues-with-the-default-field-compression-td4130173.html
> Create a benchmark for Full text search
> ---------------------------------------
>
> Key: OAK-1702
> URL: https://issues.apache.org/jira/browse/OAK-1702
> Project: Jackrabbit Oak
> Issue Type: Task
> Components: bench
> Reporter: Chetan Mehrotra
> Assignee: Chetan Mehrotra
> Fix For: 1.1
>
> Attachments: OAK-1702-lazy-cursor.patch,
> OAK-1702-shared-indexer.patch, OAK-1702.oakcodec.patch, OAK-1702.patch
>
>
> To compare the performance of Full text search between Jackrabbit 2 and Oak a
> benchmark should be added.
> To start with the benchmark would do following
> * Would be based on WikipediaImport benchmark. So it would import the
> wikipedia dump and perform full text query on that
> * Should be able to run on both JR2 and Oak. Need to account for maven setup
> to handle different Lucene version as JR2 uses 3.6.0 and Oak use 4.x
> Later we can add concurrent version
--
This message was sent by Atlassian JIRA
(v6.2#6252)
