[
https://issues.apache.org/jira/browse/LUCENE-4069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13409746#comment-13409746
]
Michael McCandless commented on LUCENE-4069:
--------------------------------------------
I ran with with the fastest configuration (lookupByReader=false,
shareEnums=true, doSortKeys=true, useDocValues=true,
doDirectDelete=true, useBase36=true).
I used MMapDir, 10M numDocs and keySpaceSize, Java 1.7.0_04, 2 GB
starting/max heap.
With doWorstCaseFlushing=false:
{noformat}
Lucene40
55978 ms
Bloom
49880 ms
Memory
55965 ms
Pulsing
56059 ms
{noformat}
With doWorstCaseFlushing=true:
{noformat}
Lucene40
61097 ms
Bloom
53698 ms
Memory
61066 ms
Pulsing
61355 ms
{noformat}
So Bloom is ~11-12% faster. Very curious that Lucene40, Pulsing and
Memory are basically the same!
> Segment-level Bloom filters for a 2 x speed up on rare term searches
> --------------------------------------------------------------------
>
> Key: LUCENE-4069
> URL: https://issues.apache.org/jira/browse/LUCENE-4069
> Project: Lucene - Java
> Issue Type: Improvement
> Components: core/index
> Affects Versions: 3.6, 4.0
> Reporter: Mark Harwood
> Priority: Minor
> Fix For: 4.0, 3.6.1
>
> Attachments: BloomFilterPostingsBranch4x.patch,
> LUCENE-4069-tryDeleteDocument.patch, MHBloomFilterOn3.6Branch.patch,
> PKLookupUpdatePerfTest.java, PKLookupUpdatePerfTest.java,
> PKLookupUpdatePerfTest.java, PrimaryKeyPerfTest40.java
>
>
> An addition to each segment which stores a Bloom filter for selected fields
> in order to give fast-fail to term searches, helping avoid wasted disk access.
> Best suited for low-frequency fields e.g. primary keys on big indexes with
> many segments but also speeds up general searching in my tests.
> Overview slideshow here:
> http://www.slideshare.net/MarkHarwood/lucene-bloomfilteredsegments
> Benchmarks based on Wikipedia content here: http://goo.gl/X7QqU
> Patch based on 3.6 codebase attached.
> There are no 3.6 API changes currently - to play just add a field with "_blm"
> on the end of the name to invoke special indexing/querying capability.
> Clearly a new Field or schema declaration(!) would need adding to APIs to
> configure the service properly.
> Also, a patch for Lucene4.0 codebase introducing a new PostingsFormat
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
