maxWarmingSearcher=1 is good for current stable Solr versions where memory is important. Overlapping warming searchers can be extremely memory consuming. I don't know how cache warming behaves with NRT.
On Wednesday 09 March 2011 11:27:39 stockii wrote: > question: http://wiki.apache.org/solr/NearRealtimeSearchTuning > > > 'PERFORMANCE WARNING: Overlapping onDeckSearchers=x > > i got this message. > in my solrconfig.xml: maxWarmingSearchers=4, if i set this to 1 or 2 i got > exception. with 4 i got nothing, but the Performance Warning. the > wiki-articel says, that the best solution is to set the warmingSearcher to > 1!!! how can this work ? > > ----- > ------------------------------- System > ---------------------------------------- > > One Server, 12 GB RAM, 2 Solr Instances, 7 Cores, > 1 Core with 31 Million Documents other Cores < 100.000 > > - Solr1 for Search-Requests - commit every Minute - 5GB Xmx > - Solr2 for Update-Request - delta every Minute - 4GB Xmx > -- > View this message in context: > http://lucene.472066.n3.nabble.com/NRT-in-Solr-tp2652689p2654696.html Sent > from the Solr - User mailing list archive at Nabble.com. -- Markus Jelsma - CTO - Openindex http://www.linkedin.com/in/markus17 050-8536620 / 06-50258350
