lucene-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Peilin Yang <>
Subject Question about threading in search
Date Sun, 03 Sep 2017 01:33:18 GMT
I was wondering if anyone can shed some light on an issue we're having:
we're comparing two different indexes on the same collection - one with
lots of different segments (default settings), and one with a force
merged into one segment. It seems that search is sometimes faster with 
multiple segments.

We thought it might be because Lucene parallelizes searching over the

But then we came across this:

where the javadoc says: "... this method will use the searcher's
ExecutorService in order to parallelize execution of the collection on
the configured leafSlices."

But we're using the vanilla search... but does the vanilla search
redirect to this anyway? Either way, we're not explicitly configuring
and ExecutorService...

Any insight on exactly what's going on?

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message