Return-Path: Delivered-To: apmail-lucene-solr-user-archive@locus.apache.org Received: (qmail 47808 invoked from network); 12 Nov 2008 19:17:18 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 12 Nov 2008 19:17:18 -0000 Received: (qmail 75378 invoked by uid 500); 12 Nov 2008 19:17:21 -0000 Delivered-To: apmail-lucene-solr-user-archive@lucene.apache.org Received: (qmail 75352 invoked by uid 500); 12 Nov 2008 19:17:21 -0000 Mailing-List: contact solr-user-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: solr-user@lucene.apache.org Delivered-To: mailing list solr-user@lucene.apache.org Received: (qmail 75341 invoked by uid 99); 12 Nov 2008 19:17:21 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 12 Nov 2008 11:17:21 -0800 X-ASF-Spam-Status: No, hits=2.6 required=10.0 tests=DNS_FROM_OPENWHOIS,SPF_HELO_PASS,SPF_PASS,WHOIS_MYPRIVREG X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of lists@nabble.com designates 216.139.236.158 as permitted sender) Received: from [216.139.236.158] (HELO kuber.nabble.com) (216.139.236.158) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 12 Nov 2008 19:16:01 +0000 Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1L0LCm-0004qD-Ih for solr-user@lucene.apache.org; Wed, 12 Nov 2008 11:16:44 -0800 Message-ID: <20467281.post@talk.nabble.com> Date: Wed, 12 Nov 2008 11:16:44 -0800 (PST) From: oleg_gnatovskiy To: solr-user@lucene.apache.org Subject: Re: Query Performance while updating teh index In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: oleg_gnatovskiy@citysearch.com References: <20452835.post@talk.nabble.com> <20467099.post@talk.nabble.com> X-Virus-Checked: Checked by ClamAV on apache.org Yonik Seeley wrote: > > On Wed, Nov 12, 2008 at 2:06 PM, oleg_gnatovskiy > 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 >>> 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.