Speed up site generation #6
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
Vim output is stored in a cache file, the name of which is taken from a hash of the input arguments to vimHighlight. During future generates these cache files are re-read instead of invoking vim again
|
Thanks for your contribution! This is really helpful. |
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.
Attempted to speed up site building by caching vim html output in separate file.
During future builds these file are queried before executing Vim command.
Filename are generated by hashing all variable input to vimHighlight, so if the codeblock is changed or updated the hash changes and Vim is executed on the new block.
Build time for my site, nxfifteen.me.uk, with 96 separate codeblocks has been decreased from 5-6 minutes to less than 1