describe performance benefits of disabling config.assets.check_precompiled_asset #441
Conversation
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
1 participant
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.
After hours of debugging long latency on the first call to
ActionView::Helpers::AssetUrlHelper.asset_pathin development, I finally discovered the performance benefits of disablingconfig.assets.check_precompiled_assetvia this issue: #352 this reduced time for the first call toasset_pathto complete from > 60 seconds to < 1 second on developer machines for our application.This pull request attempts to improve the documentation for this setting so that people trying to debug similar performance problems will have a clue to try disabling
config.assets.check_precompiled_asset.