-
Bug
-
Resolution: Fixed
-
P2
-
None
-
b17
-
generic
-
generic
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8204791 | 11.0.1 | Kim Barrett | P2 | Resolved | Fixed | team |
if ((mt_processing && ParallelRefProcBalancingEnabled) ||
_discovery_is_mt)
The new test is
if (mt_processing && ParallelRefProcBalancingEnabled)
The old test balanced unnecessarily when !mt_processing (if _discovery_is_mt), which was the point of
(1) mt_processing is true
(2) ParallelRefProcBalancingEnabled is false (not the default)
and either
(3) _discovery_is_mt is true and the number of processing threads < the number of discovery threads
or
(4) _discovery_is_mt is false and the number of processing threads < the maximum number of queues
then balancing is required but will not be performed. It is required because there are discovery queues that won't be dealt with by any processing thread. The ! _discovery_is_mt case is because discovery is done round robin style among the queues.
- backported by
-
JDK-8204791 JDK-8201487 disabled too much queue balancing
-
- Resolved
-
- relates to
-
JDK-8202328 Concurrently build indexes for rebalancing Reference lists
-
- Open
-
-
JDK-8201487 Do not rebalance reference processing queues if not doing parallel reference processing
-
- Resolved
-