Hi, We use this scenario in production where we have one write-only Solr instance and 1 read-only, pointing to the same data. We do this so we can optimize caching/etc. for each instance for write/read. The main performance gain is in cache warming and associated parameters. For your Index W, it's worth turning off cache warming altogether, so commits aren't slowed down by warming.
Peter On Sun, Feb 6, 2011 at 3:25 PM, Isan Fulia <isan.fu...@germinait.com> wrote: > Hi all, > I have setup two indexes one for reading(R) and other for writing(W).Index R > refers to the same data dir of W (defined in solrconfig via <dataDir>). > To make sure the R index sees the indexed documents of W , i am firing an > empty commit on R. > With this , I am getting performance improvement as compared to using the > same index for reading and writing . > Can anyone help me in knowing why this performance improvement is taking > place even though both the indexeses are pointing to the same data > directory. > > -- > Thanks & Regards, > Isan Fulia. >
