(I'm using Lucene 4.9.0)
I've been doing some perf testing of MemoryIndex, and have found that it is
much slower when a BooleanQuery contains a non-required clause, compared to
when it just contains required clauses.
Most of the time is spent in BooleanScorer, which as far as I can tell is an
I’m not sure about this particular error, but in general, once the JVM has
OOM’d, it is completely unreliable and should be restarted. I’m assuming Lucene
catches the OOM just so that it doesn’t get in a state where it will corrupt
the index.
-Michael
From: Tom Burton-West [mailto:tburt...@umi
