Mailing-List: contact java-commits-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: java-dev@lucene.apache.org
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Apache Wiki <wikidiffs@apache.org>
To: java-commits@lucene.apache.org
Date: Tue, 14 Apr 2009 11:10:53 -0000
Message-ID: <20090414111053.14148.57168@eos.apache.org>
Subject: [Lucene-java Wiki] Update of "ImproveSearchingSpeed" by TokeEskildsen

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Lucene-java Wiki" for change notification.

The following page has been changed by TokeEskildsen:
http://wiki.apache.org/lucene-java/ImproveSearchingSpeed

The comment on the change is:
Recommended profiling

------------------------------------------------------------------------------
  
   It can be much more efficient to restrict results to a part of the index using a cached bit set filter rather than using a query clause. This is especially true for restrictions that match a great number of documents of a large index. Filters are typically used to restrict the results to a category but could in many cases be used to replace any query clause. One difference between using a Query and a Filter is that the Query has an impact on the score while a Filter does not.
  
+  * '''Find the bottleneck.'''
+ 
+ Complex query analysis or heavy post-processing of results are examples of hidden bottlenecks for searches. Profiling with at tool such as [[https://visualvm.dev.java.net/ VisualVM]] helps locating the problem.
+