Avoid double calculation of checksum #789
Merged
Conversation
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
The new checksum of objects used to be calculated twice: 1. for checksums_available? 2. for checksums_identical? Since checksum calculation can be costly, we memoize its calculation.
This was referenced Dec 31, 2015
|
Thanks! |
denisdefreyne
added a commit
that referenced
this pull request
Dec 31, 2015
…lation Avoid double calculation of checksum
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.
The new checksum of objects is currently calculated twice:
checksums_available?checksums_identical?Since checksum calculation can be costly, this commit memoizes its calculation.
This speeds up the compilation of my site with 20% in case of no changes.