[
https://issues.apache.org/jira/browse/LUCENE-8808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16847742#comment-16847742
]
Atri Sharma commented on LUCENE-8808:
-------------------------------------
[~jpountz] Essentially, no. My proposal is basically to have a last level limit
to ensure that no single query overloads the entire system i.e. a query does
not decide to use 72 threads on a 32 core machine. We could potentially not
even have a configurable cap, and always set it to number of cores.
I am not married to this approach, so happy to hear ideas.
> Introduce Optional Cap on Number Of Threads Per Query
> -----------------------------------------------------
>
> Key: LUCENE-8808
> URL: https://issues.apache.org/jira/browse/LUCENE-8808
> Project: Lucene - Core
> Issue Type: Improvement
> Components: core/search
> Reporter: Atri Sharma
> Priority: Major
>
> With the presence of https://issues.apache.org/jira/browse/LUCENE-8757 , a
> natural progression is to allow advanced users to specify a cap on the number
> of threads a query can use. This is especially useful for long polled
> IndexSearcher instances, where the same instance is used to fire queries for
> multiple runs and there are multiple concurrent IndexSearcher instances on
> the same node.
>
> This will be an optional parameter and local only to the IndexSearcher
> instance being configured during construction.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
