Pipeline StageIterator: Improve performance and simplify #24528
+113
−60
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Refactor the pipeline
StageIteratorto skip gaps between stages, improving performance by avoiding unnecessary iteration and eliminatingmap.containsKey()checks for stage numbers that have no associated pipeline.StageIteratorin particular can be a hotspot, since it previously iterates all stages for each message that is processed (on each processor thread), this delay could add up with messages processing in serial on each processor thread.Testing
The existing unit tests still pass with this refactor (good initial sign). Initial performance testing shows roughly the execution time between two contiguous stages and far apart stages (e.g
0,int.max). Some additional tests have also been added. We should do some solid testing with this within a running application too.