Thesharing opened a new pull request #15387:
URL: https://github.com/apache/flink/pull/15387
## What is the purpose of the change
*Based on the scheduler benchmark introduced in FLINK-21731, we find that
there are two procedures related to DefaultScheduler#allocateSlots have O(N^2)
complexity:*
-
*ExecutionSlotSharingGroupBuilder#tryFindAvailableProducerExecutionSlotSharingGroupFor*
-
*ExecutionGraphToInputsLocationsRetrieverAdapter#getConsumedResultPartitionsProducers*
*Based on FLINK-21326, we can replace the usages of consumed partitions with
ConsumedPartitionGroup and optimize the complexity from O(N^2) to O(N).*
## Brief change log
- *Optimize
`ExecutionSlotSharingGroupBuilder#tryFindAvailableProducerExecutionSlotSharingGroupFor`*
- *Optimize
`ExecutionGraphToInputsLocationsRetrieverAdapter#getConsumedResultPartitionsProducers`*
## Verifying this change
*Since these optimizations don't change the original logic of related
procedures, we believe these changes should be covered by existing test cases,
such as `ExecutionGraphToInputsLocationsRetrieverAdapterTest`,
`LocalInputPreferredSlotSharingStrategyTest`, and etc.*
## Does this pull request potentially affect one of the following parts:
- Dependencies (does it add or upgrade a dependency): (yes / **no**)
- The public API, i.e., is any changed class annotated with
`@Public(Evolving)`: (yes / **no**)
- The serializers: (yes / **no** / don't know)
- The runtime per-record code paths (performance sensitive): (yes / **no**
/ don't know)
- Anything that affects deployment or recovery: JobManager (and its
components), Checkpointing, Kubernetes/Yarn/Mesos, ZooKeeper: (**yes** / no /
don't know)
- The S3 file system connector: (yes / **no** / don't know)
## Documentation
- Does this pull request introduce a new feature? (yes / **no**)
- If yes, how is the feature documented? (**not applicable** / docs /
JavaDocs / not documented)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
