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

Michael McCandless commented on LUCENE-2840:
--------------------------------------------

bq. You frequently quote "progress, not perfection" in relation to the code, 
but why don't we apply this same principle to our threading guarantees?

Oh we should definitely apply progress not perfection here -- in fact we 
already are: for starters (today), we bind concurrency to segments (so eg an 
"optimized" index has no concurrency), and we just use an ES (punt this thread 
scheduling problem to the caller).  This is better than nothing, but not good 
enough -- we can do better.

There's another quote that applies here: "big dreams, small steps".  My comment 
above is "dreaming" but when it comes time to actually get the real work done / 
making progress towards that dream, of course we take baby steps / progress not 
perfection.

Design discussions should start w/ the big dreams but then once you've got a 
rough sense of where you want to get to in the future you shift back to the 
baby steps you do today, in the direction of that future goal.

Maybe I should wrap my comments in </dream> tags and </babysteps> tags!

> Multi-Threading in IndexSearcher (after removal of MultiSearcher and 
> ParallelMultiSearcher)
> -------------------------------------------------------------------------------------------
>
>                 Key: LUCENE-2840
>                 URL: https://issues.apache.org/jira/browse/LUCENE-2840
>             Project: Lucene - Java
>          Issue Type: Sub-task
>          Components: Search
>            Reporter: Uwe Schindler
>            Priority: Minor
>             Fix For: 4.0
>
>
> Spin-off from parent issue:
> {quote}
> We should discuss about how many threads should be spawned. If you have an 
> index with many segments, even small ones, I think only the larger segments 
> should be separate threads, all others should be handled sequentially. So 
> maybe add a maxThreads cound, then sort the IndexReaders by maxDoc and then 
> only spawn maxThreads-1 threads for the bigger readers and then one 
> additional thread for the rest?
> {quote}

-- 
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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Reply via email to