You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Michael McCandless (JIRA)" <ji...@apache.org> on 2019/07/22 19:51:00 UTC
[jira] [Commented] (LUCENE-8865) Use incoming thread for execution
if IndexSearcher has an executor
[ https://issues.apache.org/jira/browse/LUCENE-8865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16890429#comment-16890429 ]
Michael McCandless commented on LUCENE-8865:
--------------------------------------------
Alas, I ran our internal benchmarks (production queries on production documents, measuring red-line QPS and long-pole query latencies at 10% capacity) and I could not measure any change due to this fix – it seems to be in the noise.
I was hoping for a small gain due to one fewer thread context switch ... but I still think the change is a good one! Thanks [~simonw]!
> Use incoming thread for execution if IndexSearcher has an executor
> -------------------------------------------------------------------
>
> Key: LUCENE-8865
> URL: https://issues.apache.org/jira/browse/LUCENE-8865
> Project: Lucene - Core
> Issue Type: Improvement
> Reporter: Simon Willnauer
> Priority: Major
> Fix For: master (9.0), 8.2
>
> Time Spent: 3h 20m
> Remaining Estimate: 0h
>
> Today we don't utilize the incoming thread for a search when IndexSearcher
> has an executor. This thread is only idleing but can be used to execute a search
> once all other collectors are dispatched.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org