Lower your mergeFactor and Lucene will merge segments(i.e. fewer index files) and purge deletes more often for you at the expense of somewhat slower indexing.
Otis -- Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch ----- Original Message ---- > From: wojtekpia <wojte...@hotmail.com> > To: solr-user@lucene.apache.org > Sent: Tuesday, January 6, 2009 5:18:26 PM > Subject: Re: Snapinstaller vs Solr Restart > > > I'm optimizing because I thought I should. I'll be updating my index > somewhere between every 15 minutes, and every 2 hours. That means between 12 > and 96 updates per day. That seems like a lot of index files (and it scared > me a little), so that's my second reason for wanting to optimize nightly. > > I haven't benchmarked the performance hit for not optimizing. That'll be my > next step. If the hit isn't too bad, I'll look into optimizing less > frequently (weekly, ...). > > Thanks Otis! > > > Otis Gospodnetic wrote: > > > > OK, so that question/answer seems to have hit the nail on the head. :) > > > > When you optimize your index, all index files get rewritten. This means > > that everything that the OS cached up to that point goes out the window > > and the OS has to slowly re-cache the hot parts of the index. If you > > don't optimize, this won't happen. Do you really need to optimize? Or > > maybe a more direct question: why are you optimizing? > > > > > > Regarding autowarming, with such high fq hit rate, I'd make good use of fq > > autowarming. The result cache rate is lower, but still decent. I > > wouldn't turn off autowarming the way you have. > > > > > > -- > View this message in context: > http://www.nabble.com/Snapinstaller-vs-Solr-Restart-tp21315273p21320334.html > Sent from the Solr - User mailing list archive at Nabble.com.