Cache invariants (repo_name, git_dir, toplevel_dir) to speed up processing large commits - #218
Open
smokris wants to merge 2 commits into
Open
smokris wants to merge 2 commits into
smokris wants to merge 2 commits into
Conversation
Copy link
Copy Markdown
Sorry, something went wrong.
…ssing large commits.
Copy link
Copy Markdown
Author
|
(Those same 7 test errors occur before the changes in this PR, too.) |
Sorry, something went wrong.
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.
git-commit-notifier was taking about 6 minutes to process a large commit in one of my repos. I ran ruby-prof and noticed that it was shelling out to git thousands of times to get the same information (repo name and directory info). I added caches for that data, which reduces the time to about 10 seconds.