fix: avoid O(n^2) algorithm in cleanUpGlobalClassValue #898 #910
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.
Fixes:
Instead of removing elements from
toRemovearray while traversing it, which forces rewrite of the whole array each time, create a separate arraytoRemoveReallywith elements that need to be removed.Testing done
We're running our Jenkins instance on a patched version since March 2025. The instance has more than 10k jobs, almost all created with Groovy code by Jenkins DSL plugin. There was a dramatic drop of Jenkins CPU usage when the plugin was updated with with this change. We rebased the change several times since.
Submitter checklist
This is a performance change — it is not clear how to create a test case that demonstrates the change in a reasonable time.