The real questions are: * how much often do you commit (either explicitly or automatically)? * how much segments do you allow? If you only allow 1 segment, then that whole segment is recreated using the old documents and the updates. And yes, that requires reading the old segment. It is common to allow multiple segments when you update often, so updating does not interfere with reading the index too often.
> On 4 Jun 2020, at 14:08, Anshuman Singh <singhanshuma...@gmail.com> wrote: > > I noticed that while indexing, when commit happens, there is high disk read > by Solr. The problem is that it is impacting search performance when the > index is loaded from the disk with respect to the query, as the disk read > speed is not quite good and the whole index is not cached in RAM. > > When no searching is performed, I noticed that disk is usually read during > commit operations and sometimes even without commit at low rate. I guess it > is read due to segment merge operations. Can it be something else? > If it is merging, can we limit disk IO during merging?
