[infinispan-issues] [JBoss JIRA] (ISPN-10929) ClusterPublisher reduction combineStages concurrency level is too high

[Dan Berindei (Jira)]

     [ https://issues.jboss.org/browse/ISPN-10929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dan Berindei updated ISPN-10929:
--------------------------------
           Status: Resolved  (was: Pull Request Sent)
    Fix Version/s: 10.1.0.Beta1
       Resolution: Done


> ClusterPublisher reduction combineStages concurrency level is too high
> ----------------------------------------------------------------------
>
>                 Key: ISPN-10929
>                 URL: https://issues.jboss.org/browse/ISPN-10929
>             Project: Infinispan
>          Issue Type: Bug
>          Components: Core
>            Reporter: Will Burns
>            Assignee: Will Burns
>            Priority: Major
>             Fix For: 10.1.0.Beta1
>
>
> The combineStages method in ClusterPublisherImpl currently uses flatMap without an explicit concurrency level. That means it will subscribe to up to 128 futures at the same time. This isn't a problem when only in memory is used as the stages are completed as they are received. However when a segmented store is in play, this means it will process 128 segments at the same time, even when doing sequential publisher.
> We should instead limit the concurrency to the cpuCount when the publisher is parallel and just 1 when it is sequential. The latter matches how many threads the upstream publisher will use as well.



--
This message was sent by Atlassian Jira
(v7.13.8#713008)