Details
-
Improvement
-
Status: Closed
-
Major
-
Resolution: Duplicate
-
1.10.0
-
None
-
None
Description
Currently RegionPartitionReleaseStrategy and AdaptedRestartPipelinedRegionStrategyNG both need to compute distinct pipelined regions, which affects the performance due to the duplicate calculating.
The best idea that comes to my mind so far is calculating distinct pipelined regions in DefaultExecutionTopology so that we can remove the duplicate calculating.
Attachments
Issue Links
- duplicates
-
FLINK-17180 Implement PipelinedRegion interface for SchedulingTopology
- Closed