Return-Path: Delivered-To: apmail-lucene-java-user-archive@www.apache.org Received: (qmail 9911 invoked from network); 26 May 2007 16:15:53 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 26 May 2007 16:15:53 -0000 Received: (qmail 28581 invoked by uid 500); 26 May 2007 16:15:52 -0000 Delivered-To: apmail-lucene-java-user-archive@lucene.apache.org Received: (qmail 28281 invoked by uid 500); 26 May 2007 16:15:51 -0000 Mailing-List: contact java-user-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: java-user@lucene.apache.org Delivered-To: mailing list java-user@lucene.apache.org Received: (qmail 28270 invoked by uid 99); 26 May 2007 16:15:51 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 26 May 2007 09:15:51 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of yseeley@gmail.com designates 64.233.166.183 as permitted sender) Received: from [64.233.166.183] (HELO py-out-1112.google.com) (64.233.166.183) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 26 May 2007 09:15:44 -0700 Received: by py-out-1112.google.com with SMTP id a25so1616687pyi for ; Sat, 26 May 2007 09:15:23 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=SpRmAK0dQqowTxOiPu7TzdljcC+f9hcpvzz8GMtjsRTBLrtM76DJp+MibPMbksXQ8GrpbMxdNGfTl973HUms1ZQAE/v9dE700fELsgcxRweUdqHDCD4aGS3vUyLISw6ErTa+QsZaIv+Lci18Ipvxizmfs566RpFGvyr4Hf0cmwA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=ltu69RB2tdcGl5Nl9LAsrZRpG5iv2SRUhU+X/M1z30em1gOwh41I0QOEQiaTQEQ/8w4tbrkdV+Y3WMuwtMSuUe5nT8jZSKa1G8+GKQCGs16aEU/ienKrDi4q2LLX1wtcsrrSxalVXfCGMa8eX8jE4N0EumBjZtPrbXAu7JDrL0U= Received: by 10.35.109.2 with SMTP id l2mr4646365pym.1180196123769; Sat, 26 May 2007 09:15:23 -0700 (PDT) Received: by 10.35.98.7 with HTTP; Sat, 26 May 2007 09:15:23 -0700 (PDT) Message-ID: Date: Sat, 26 May 2007 12:15:23 -0400 From: "Yonik Seeley" Sender: yseeley@gmail.com To: java-user@lucene.apache.org Subject: Re: Searching on a Rapidly changing Index In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20070524092205.GH5135@thegestalt.org> <359a92830705240628r5902dd41rcb5c7bceade2014b@mail.gmail.com> X-Google-Sender-Auth: 9c2ceced6d7c10f5 X-Virus-Checked: Checked by ClamAV on apache.org On 5/24/07, Joe Shaw wrote: > On 5/24/07, Erick Erickson wrote: > > If that's unacceptable, you can *still* open up a new reader in the > > background and warm it up before using it. "immediately" then > > becomes 5-10 seconds or so. > > I've seen the term "warming" used a few times on the various lists. > What constitutes warming up a searcher, simply running a dummy query? Yes, but not too dumb ;-) Most important is to sort on commonly used sort fields to populate the field caches. Solr takes this further, allowing statically configured queries, but also pre-populating query and filter caches based on the most-recently-used entries in the existing searcher. -Yonik --------------------------------------------------------------------- To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org For additional commands, e-mail: java-user-help@lucene.apache.org