lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael McCandless (JIRA)" <>
Subject [jira] Resolved: (LUCENE-1265) Identify bottleneck associated with not pooling searchers
Date Mon, 17 Nov 2008 10:30:44 GMT


Michael McCandless resolved LUCENE-1265.

    Resolution: Duplicate

Dup of LUCENE-1329 (readOnly IndexReader) and LUCENE-753 (NIOFSDirectory), at least on non-Windows

Based on this user report it seems like sharing an IndexReader across multiple threads in
fact gives better performance than thread-private IndexReader instances:

> Identify bottleneck associated with not pooling searchers
> ---------------------------------------------------------
>                 Key: LUCENE-1265
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Task
>          Components: Search
>            Reporter: Karl Wettin
> There have been multiple reports suggesting synchronization problems due to great search
performace boost while pooling searchers under heavy load.
> I think this should be confirmed. Then identified and fixed,  alternatively add such
a pool to the code base. 
> Use one instance of  IndexSearcher.
> Share a single  IndexSearcher across queries and across threads in your application.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message