[
https://issues.apache.org/jira/browse/LUCENE-8757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16834525#comment-16834525
]
Simon Willnauer commented on LUCENE-8757:
-----------------------------------------
[~atris] actually I thought about these defaults again and I am starting to
think it's an ok default. The reason for this is that we try to prevent having
dedicated threads for smallish segments so we group them together. I still do
wonder if we need to have 2 parameters? Wouldn't it be enough to just say that
we group things together until we have at least 250k docs per thread to be
searched? is it really necessary to have another parameter that limits the
number of segmetns per slice? I think a single parameter would be great and
simpler. WDYT?
> Better Segment To Thread Mapping Algorithm
> ------------------------------------------
>
> Key: LUCENE-8757
> URL: https://issues.apache.org/jira/browse/LUCENE-8757
> Project: Lucene - Core
> Issue Type: Improvement
> Reporter: Atri Sharma
> Priority: Major
> Attachments: LUCENE-8757.patch
>
>
> The current segments to threads allocation algorithm always allocates one
> thread per segment. This is detrimental to performance in case of skew in
> segment sizes since small segments also get their dedicated thread. This can
> lead to performance degradation due to context switching overheads.
>
> A better algorithm which is cognizant of size skew would have better
> performance for realistic scenarios
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
