lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Simon Willnauer (JIRA)" <>
Subject [jira] [Commented] (LUCENE-8757) Better Segment To Thread Mapping Algorithm
Date Fri, 03 May 2019 08:29:00 GMT


Simon Willnauer commented on LUCENE-8757:

Thanks [~atris], can you bring back the javadocs for 
protected LeafSlice[] slices(List<LeafReaderContext> leaves){code}

please don't reassign an argument like here:

leaves = new ArrayList<>(leaves);

The rest of the patch looks OK to me yet I am not so sure about the defaults. I do wonder
if we should look at this from a different perspective. Rather than using hard numbers can
we try to evenly balance the total number of documents across N threads and make N the variable?
[~mikemccand] WDYT?

> Better Segment To Thread Mapping Algorithm
> ------------------------------------------
>                 Key: LUCENE-8757
>                 URL:
>             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
> A better algorithm which is cognizant of size skew would have better performance for
realistic scenarios

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message