[
https://issues.apache.org/jira/browse/LUCENE-8757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16834065#comment-16834065
]
Atri Sharma commented on LUCENE-8757:
-------------------------------------
Hi [~simonw],
Spending a bit more time thinking about your suggestions, I agree that it is a
great idea, albeit requiring more thought and effort than what this Jira
proposes to achieve.
I have opened LUCENE-8794 - Cost Based Slice Allocation Algorithm for
discussing the same. Please share your thoughts.
Would it make sense to push this patch, and then let users consume it and
provide feedback while we iterate on the more sophisticated version? We could
even have both of the methods available as options to users, potentially
Thoughts?
> 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
