lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yonik Seeley (JIRA)" <j...@apache.org>
Subject [jira] Commented: (LUCENE-1265) Identify bottleneck associated with not pooling searchers
Date Thu, 17 Apr 2008 16:31:22 GMT

    [ https://issues.apache.org/jira/browse/LUCENE-1265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12590089#action_12590089
] 

Yonik Seeley commented on LUCENE-1265:
--------------------------------------

I think IndexInput is the right place to fix it (assuming the sync bottleneck is during seek+read).

> Identify bottleneck associated with not pooling searchers
> ---------------------------------------------------------
>
>                 Key: LUCENE-1265
>                 URL: https://issues.apache.org/jira/browse/LUCENE-1265
>             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. 
> http://www.nabble.com/Multiple-searchers-%28Was%3A-CachingWrapperFilter%3A-why-cache-per-IndexReader-%29-td14916124.html#a14997611
> http://www.nabble.com/Solid-State-Drives-vs.-RAMDirectory-td16025864.html
> http://wiki.apache.org/lucene-java/ImproveSearchingSpeed
> 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: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org


Mime
View raw message