[GitHub] [lucene-solr] atris commented on issue #854: Shared PQ Based Early Termination for Concurrent Search

2019-09-12 Thread GitBox
atris commented on issue #854: Shared PQ Based Early Termination for Concurrent Search URL: https://github.com/apache/lucene-solr/pull/854#issuecomment-530678743 > > RE: synchronization, what are your thoughts on using a global shared array where each collector publishes its bottom value

[GitHub] [lucene-solr] atris commented on issue #854: Shared PQ Based Early Termination for Concurrent Search

2019-09-11 Thread GitBox
atris commented on issue #854: Shared PQ Based Early Termination for Concurrent Search URL: https://github.com/apache/lucene-solr/pull/854#issuecomment-530675406 > There is also the option of something in between. To avoid thread contention, could we just make uncoordinated read/write of

[GitHub] [lucene-solr] atris commented on issue #854: Shared PQ Based Early Termination for Concurrent Search

2019-09-11 Thread GitBox
atris commented on issue #854: Shared PQ Based Early Termination for Concurrent Search URL: https://github.com/apache/lucene-solr/pull/854#issuecomment-530509226 > I think we're talking of different approaches, hence the confusion. It is correct that we can start setting the minimum score

[GitHub] [lucene-solr] atris commented on issue #854: Shared PQ Based Early Termination for Concurrent Search

2019-09-11 Thread GitBox
atris commented on issue #854: Shared PQ Based Early Termination for Concurrent Search URL: https://github.com/apache/lucene-solr/pull/854#issuecomment-530453877 > We need to ensure that the minimum score of the slice can be set as the maximum minimum score for all slices, however if

[GitHub] [lucene-solr] atris commented on issue #854: Shared PQ Based Early Termination for Concurrent Search

2019-09-11 Thread GitBox
atris commented on issue #854: Shared PQ Based Early Termination for Concurrent Search URL: https://github.com/apache/lucene-solr/pull/854#issuecomment-530418576 > I think it would be simpler to keep the maximum minimum score on each slice. Each time a slice publish a new minimum

[GitHub] [lucene-solr] atris commented on issue #854: Shared PQ Based Early Termination for Concurrent Search

2019-09-11 Thread GitBox
atris commented on issue #854: Shared PQ Based Early Termination for Concurrent Search URL: https://github.com/apache/lucene-solr/pull/854#issuecomment-530380308 > I am not sure that synchronization would be an issue in this model since the update of the global min score should be quick,

[GitHub] [lucene-solr] atris commented on issue #854: Shared PQ Based Early Termination for Concurrent Search

2019-09-11 Thread GitBox
atris commented on issue #854: Shared PQ Based Early Termination for Concurrent Search URL: https://github.com/apache/lucene-solr/pull/854#issuecomment-530349367 > I think that you need to ensure that the slice publishing the new min score is full, otherwise the min score cannot be the

[GitHub] [lucene-solr] atris commented on issue #854: Shared PQ Based Early Termination for Concurrent Search

2019-09-11 Thread GitBox
atris commented on issue #854: Shared PQ Based Early Termination for Concurrent Search URL: https://github.com/apache/lucene-solr/pull/854#issuecomment-530343716 > > Is this proposal to continue collecting the full N per slice (thread work unit), until some/all of them have a full (top N)

[GitHub] [lucene-solr] atris commented on issue #854: Shared PQ Based Early Termination for Concurrent Search

2019-09-05 Thread GitBox
atris commented on issue #854: Shared PQ Based Early Termination for Concurrent Search URL: https://github.com/apache/lucene-solr/pull/854#issuecomment-528247486 > I thought that the follow up for LUCENE-8939 would be to allow the sharing of the minimum score (could be extended to a

[GitHub] [lucene-solr] atris commented on issue #854: Shared PQ Based Early Termination for Concurrent Search

2019-09-04 Thread GitBox
atris commented on issue #854: Shared PQ Based Early Termination for Concurrent Search URL: https://github.com/apache/lucene-solr/pull/854#issuecomment-527823824 cc @jpountz. This PR builds on top of #831 This is an