It's generally recommended that you do the indexing on the master and searches on the slaves. In that case, firstSearcher and newSearcher sections are irrelevant on the master and shouldn't be there.
I don't understand why you would need 5 more machines, are you sharding? Best Erick On Thu, Jan 19, 2012 at 7:25 AM, Daniel Brügge <daniel.brue...@googlemail.com> wrote: > Hi, > > I am currently running multiple Solr instances and often write data to > them. I also query them. Both works fine right now, because I don't have so > many search requests. For querying I recognized that the firstSearcher and > newSearcher static warming with one facet query really brings a performance > boost. But the downside is, that writing now is really slow. > > Does it make sense at all to place firstSearcher and newSearcher on a Solr > server, which get lot's of writes. Or is the best strategy to introduce > some slave server, where these event listeners are integrated, but to keep > them away from the master? > > The thing is, that I would need 6 additional Solr slaves, if I would pick > this approach. :) > > What do you think? > > Thanks. > Daniel