-
Notifications
You must be signed in to change notification settings - Fork 119
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[JENKINS-12763] Reduce lock contention while updating caches #21
Merged
Merged
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
There are no files selected for viewing
This file contains 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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Better to make the diff not touch any more lines than it absolutely has to, so it can be more easily reviewed and is less likely to conflict with other changes. I think you are only really changing a couple things here but it is hard to see that. (OK for indentation to not quite match brace structure.)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's been 4 months since I pushed this, so I will try to sum up the whole idea again in a single additional comment in this review. It's not that easy to analyze it by looking at some lines on isolation, as basically the change from the single lock scheme to a double one changes many parts of the affected method.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
But looking at the diff, it seems like a lot of lines changed only in indentation, i.e. you are wrapping some areas of code in try-blocks differently. It would just be easier to see what those changes are if they were not mixed up with unnecessary whitespace changes. Also if there is ever a need to examine history of those interior lines, annotate is going to be useless if their indentation changed.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The change in indentation is a consequence of the actual change in the way the master lock is handled: operations that in the original implementation were performed after obtaining the only lock used are now safely performed before obtaining the lock for the master. That is why they refer to master* variables and are placed before the try block.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I understand that the block nesting changes as part of the change in behavior. What I am requesting is that indentation of code lines be left untouched wherever possible, even if that no longer matches block nesting. In other words
should be avoided in favor of the minimized diff
which merges better, annotates better, and is reviewed more readily (since it is obvious where the interior block was modified if at all). Ideally SCMs like Git would understand block structure in programming languages and behave more intelligently, but as a rule they do not.