ext:
> http://lucene.472066.n3.nabble.com/Replication-process-on-Master-Slave-slowing-down-slave-read-search-performance-tp707934p4078090.html
> Sent from the Solr - User mailing list archive at Nabble.com.
://lucene.472066.n3.nabble.com/Replication-process-on-Master-Slave-slowing-down-slave-read-search-performance-tp707934p4078090.html
Sent from the Solr - User mailing list archive at Nabble.com.
You don't need multi-core. Solr already does this automatically. It creates a
new Searcher and auto-warms the cache.
But, it will still be slow. If you use auto-warming, it uses most of one CPU,
which slows down queries during warming. Also, warming isn't perfect, so
queries will be slower afte
Hi Marcin,
This is because when you do the replication, all the caches are rebuild
cause the index has changed, so the searchs performance decrease. You can
change your architecture to a multicore one to reduce the impact of the
replication. Using two cores, one to do the replication, and other to
Hi guys,
I have noticed that Master/Slave replication process is slowing down
slave read/search performance during replication being done.
please help
cheers
