And you have searcher warming set up? Does it use sort and do your queries use sort? What do your cache settings look like?
How big is your index, how much RAM does your machine have, how much heap does the JVM have, what does vmstat output look like during warm-up? ... Otis -- Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch ________________________________ From: oleg_gnatovskiy <[EMAIL PROTECTED]> To: solr-user@lucene.apache.org Sent: Wednesday, November 12, 2008 2:16:44 PM Subject: Re: Query Performance while updating teh index Yonik Seeley wrote: > > On Wed, Nov 12, 2008 at 2:06 PM, oleg_gnatovskiy > <[EMAIL PROTECTED]> wrote: >> The rsync seems to have nothing to do with slowness, because while the >> rsync >> is going on, there isn't any reload occurring, once the files are on the >> system, it tries a curl request to reload the searcher, which at that >> point >> causes the delays. The file transfer probably has nothing to do with >> this. >> Does this mean that it happens during warming? > > Yes, it would seem so. > It could either be that 1) warming the new reader slows down the > current reader used to service queries > or 2) the first queries to come into the new reader are slow (which > can be solved with some static warming queries to load sort fields, > facet caches, etc). > > How many CPUs does the box have that you are running on? What OS? > > -Yonik > > > >> Yonik Seeley wrote: >>> >>> On Tue, Nov 11, 2008 at 9:31 PM, oleg_gnatovskiy >>> <[EMAIL PROTECTED]> wrote: >>>> Hello. We have an index with 15 million documents working on a >>>> distributed >>>> environment, with an index distribution setup. While an index on a >>>> slave >>>> server is being updated, query response times become extremely slow >>>> (upwards >>>> of 5 seconds). Is there any way to decrease the hit query response >>>> times >>>> take while an index is being pushed? >>> >>> Can you tell why it's getting slow? Is this during warming, or does >>> it begin during the actual transfer of the new index? >>> >>> One possibility is that the new index being copied forces out parts of >>> the old index from the OS cache. More memory would help in that >>> scenario. >>> >>> -Yonik >>> >>> >> >> -- >> View this message in context: >> http://www.nabble.com/Query-Performance-while-updating-the-index-tp20452835p20467099.html >> Sent from the Solr - User mailing list archive at Nabble.com. >> >> > > 8 CPUs and Linux OS -- View this message in context: http://www.nabble.com/Query-Performance-while-updating-the-index-tp20452835p20467281.html Sent from the Solr - User mailing list archive at Nabble.com.
