Return-Path: Delivered-To: apmail-lucene-java-user-archive@www.apache.org Received: (qmail 55991 invoked from network); 26 Aug 2006 19:53:35 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 26 Aug 2006 19:53:35 -0000 Received: (qmail 79593 invoked by uid 500); 26 Aug 2006 19:53:29 -0000 Delivered-To: apmail-lucene-java-user-archive@lucene.apache.org Received: (qmail 79555 invoked by uid 500); 26 Aug 2006 19:53:29 -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 79544 invoked by uid 99); 26 Aug 2006 19:53:29 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 26 Aug 2006 12:53:29 -0700 X-ASF-Spam-Status: No, hits=0.5 required=10.0 tests=DNS_FROM_RFC_ABUSE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of paul.borgermans@gmail.com designates 64.233.182.190 as permitted sender) Received: from [64.233.182.190] (HELO nf-out-0910.google.com) (64.233.182.190) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 26 Aug 2006 12:53:28 -0700 Received: by nf-out-0910.google.com with SMTP id b2so960314nfe for ; Sat, 26 Aug 2006 12:53:07 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=H9EZOBBwOuZN4/2Tp4vzC+xHgioMjpZIZz6MCyzVfqwzjGBOPOsx2pQGHn+9nnByXUyF68/BY/KgNXB0zcwgj16wgFp7n9HuNpoEbwJq+aYD4bFKAe63/mbPY9AJgEzwJfsmorIUxLz0rb8FDYWRAxNU9X/fZnvA97TGQy1VH6I= Received: by 10.48.162.15 with SMTP id k15mr7004318nfe; Sat, 26 Aug 2006 12:53:07 -0700 (PDT) Received: by 10.49.27.13 with HTTP; Sat, 26 Aug 2006 12:53:07 -0700 (PDT) Message-ID: <8c0c601f0608261253s75939408w26a44000b48fe296@mail.gmail.com> Date: Sat, 26 Aug 2006 21:53:07 +0200 From: "Paul Borgermans" To: java-user@lucene.apache.org, "=?ISO-8859-1?Q?Martin_K=F6bele?=" Subject: Re: How to warm up In-Reply-To: <200608260911.33740.martin.kobele@netsweeper.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <200608260911.33740.martin.kobele@netsweeper.com> X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Hi It are mainly the internal caches that are of interest. If you use sorting other than the default relevance for example, use a warmin up search that uses a custom sort. You may also look at what happens in Solr (http://incubator.apache.org/solr/) related to caching. I use Java Lucene from a PHP based frontend and found that just using a Java object cache (like ehcache) can speed up searches a lot by caching filters that implement security rules for instance. I guess this also applies to pure Java implementations where Lucene does not caches on its own. hth --paul On 8/26/06, Martin Kobele wrote: > Hi, > > I have read it several times that sometimes it is practical to warm up a > searcher. What exactly does that mean? Would I simply perform a search > for "foo bar" or something like that? What happens inside the searcher so > that it becomes 'warmed up'? > > Thank you! > > Regards, > Martin > > --------------------------------------------------------------------- > To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org > For additional commands, e-mail: java-user-help@lucene.apache.org > > -- http://walhalla.wordpress.com --------------------------------------------------------------------- To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org For additional commands, e-mail: java-user-help@lucene.apache.org