You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 4, 2020. It is now read-only.
In theory the caching should protect updates from happening constantly (needlessly). Without some mechanism to tie some sort of clear cache mechanism to an update having happened on this chef run the protection does not happen in practice. In fact without a clear cache every chef run results in an attempted update if there is any difference between circonus and the local copy. This is VERY slow to be doing every chef run.
Suggested solution: Trigger a cache clear at the end of the run if we perceive a difference that needed to be updated for.
The text was updated successfully, but these errors were encountered:
In theory the caching should protect updates from happening constantly (needlessly). Without some mechanism to tie some sort of clear cache mechanism to an update having happened on this chef run the protection does not happen in practice. In fact without a clear cache every chef run results in an attempted update if there is any difference between circonus and the local copy. This is VERY slow to be doing every chef run.
Suggested solution: Trigger a cache clear at the end of the run if we perceive a difference that needed to be updated for.
The text was updated successfully, but these errors were encountered: