fix: avoid O(n^2) algorithm in cleanUpGlobalClassValue #898#910
Open
tometzky wants to merge 1 commit intojenkinsci:masterfrom
Open
fix: avoid O(n^2) algorithm in cleanUpGlobalClassValue #898#910tometzky wants to merge 1 commit intojenkinsci:masterfrom
tometzky wants to merge 1 commit intojenkinsci:masterfrom
Conversation
|
Sorry to ping @jglick / @dwnusbaum but this seems to have been the way to go for the most recent merge :). All the coverage warnings are caused by tests not testing the As @tometzky mentioned this was "battle tested" on our instance for almost a year at this point. |
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
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.