I'm developing a site (currently single server) that uses localsolr to perform geo searches on ~200,000 small records although I'm expecting this to grow significantly once I go live.
So far, so good but I've noticed that after any updates / deletions to the index the first query is then very slow (typically 3 secs compared to 0.01). Subsequent queries are then fine until the next update / deletion. Having read the documentation - it seems that this is expected behaviour but it is unclear to me on the best way to resolve it - I'm expecting many updates throughout the day and obviously don't want query performance to suffer. Am I right in assuming that if I add an additional server and setup replication (using one for updates and the other for queries) this will resolve my issue? Although it doesn't need to be realtime - I would like updates to be live within ~5 minutes. I'm quickly getting confused with multi-core, replication options, distributed SOLR, Collection Scripts etc. etc. Is there any documentation on the best circumstances for using each of these technologies? Many thanks, Tom PS. I'm using SOLR1.3/LocalSolrR2. -- View this message in context: http://www.nabble.com/Initial-query-performance-poor-after-update---delete-tp22732463p22732463.html Sent from the Solr - User mailing list archive at Nabble.com.
