lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Atri Sharma (JIRA)" <>
Subject [jira] [Commented] (LUCENE-8757) Better Segment To Thread Mapping Algorithm
Date Tue, 07 May 2019 15:09:00 GMT


Atri Sharma commented on LUCENE-8757:

Hi [~simonw]

bq. if the previous segment was smallish then group is non-null? I think you should test these
cases, maybe add a random test and randomize the order or the segments?

I dont think that case is possible, since we sort LeafReaderContexts based on the number of
documents per segment in descending order. Hence, no LeafReaderContext can be succeded by
one which has more documents than its predecessor. I agree with your thought of having a random
test with variety of configurations for segment size distributions.

bq.can and should be replaced by:

Fixed, thanks. 



> 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, LUCENE-8757.patch, 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