Repository navigation
Avoid allocations on every progress tick - #4479
Merged
vogella merged 1 commit intoOct 13, 2026
Merged
Conversation
Contributor
Every worked() and subTask() of a running job goes through refreshJobInfo, which allocated a capturing predicate and a stream over the progress listeners. During builds and indexing this runs for every unit of work reported. Filter the listeners in a plain loop instead. Assisted-by: multiple AI agents and layers of automated tooling 🤖
vogella
force-pushed
the
lv/progress-tick-allocations
branch
from
October 12, 2026 22:19
1e35e48 to
2068b7c
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Every worked() and subTask() call of a running job goes through ProgressManager.refreshJobInfo, which allocated a capturing predicate and a stream over the progress listeners each time. During builds and indexing this happens for every unit of work a job reports. The listeners are now filtered in a plain loop, which reduces the allocations per progress tick while the behaviour stays the same.