DEBUG: Add logs between fetch data and caching #755
Merged
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.
Following the log debug session on Slack I see that these lines can take up to 15 minutes to execute. It could be some freakishly slow API calls or STM live- or deadlocking.
The PR adds some logging in between these.
Suspicious logs:
In this ☝️ instance it looks like 12 minutes spent between polling the parent hash and just before fetching the data, then 3s to fetch the data and write to cache.
In this ☝️ one 17 minutes go past that include fetching data and writing it to the cache.