[
https://issues.apache.org/jira/browse/LUCENE-2041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12775927#action_12775927
]
Uwe Schindler commented on LUCENE-2041:
---------------------------------------
Oh I didn't see your patch. But its not so different, I also did lots of code
cleanup.
I also used ReentrantLocks. I added a new DummyLock to utils, that is a
replacement for ReentrantLock, but does simply nothing. By this, the
synchronized around the HitQueue in MultiSearcher can be ommitted.
> Complete parallelizaton of ParallelMultiSearcher
> ------------------------------------------------
>
> Key: LUCENE-2041
> URL: https://issues.apache.org/jira/browse/LUCENE-2041
> Project: Lucene - Java
> Issue Type: Improvement
> Components: Search
> Affects Versions: 2.9
> Reporter: Joey Surls
> Assignee: Uwe Schindler
> Priority: Minor
> Fix For: 3.0
>
> Attachments: LUCENE-2041-refactor.patch, LUCENE-2041-refactor.patch,
> LUCENE-2041.patch, LUCENE-2041.patch, LUCENE-2041.patch, LUCENE-2041.patch,
> LUCENE-2041.patch, LUCENE_2041.patch
>
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> ParallelMultiSearcher is parallel only for the method signatures of 'search'.
> Part of a query process calls the method docFreq(). There was a TODO comment
> to parallelize this. Parallelizing this method actually increases the
> performance of a query on multiple indexes, especially remotely.
--
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-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-dev-h...@lucene.apache.org
