lucene-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Riccardo Tasso <riccardo.ta...@gmail.com>
Subject Re: Optimizing number of segments in lucene index (no writes/deletes, only reads)
Date Wed, 14 Jun 2017 06:33:57 GMT
Hi,
 I have recently read this post, I think it will give you some hint:

http://blog.trifork.com/2011/11/21/simon-says-optimize-is-bad-for-you/

Probably the only advantage of having one huge segment is to use less disk
space.

Riccardo

2017-06-14 5:23 GMT+02:00 Tom Hirschfeld <tomhirschfeld@gmail.com>:

> Hello Fellow Lucene-eers,
>
> I have a lucene 6.5.1 app primarily indexed/searched via the
> latLonDocValuesField. The index is built once, and has no writes/deletes in
> production. At indexing time, we need to select the number of segments we
> want to generate, and it is unclear to us how many segments we should
> generate if we are optimizing for query speed. My intuition says that we
> should only generate 1 segment as we will have no writes/deletes, but I
> cannot find any hard evidence online to support or refute that hypothesis.
> Does anyone here know how many segments we should use? 1 segment? 1 segment
> per cpu in prod? 1 segment per core in prod? Something else?
>
> Best,
> Tom Hirschfeld
>

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