Disable task cache for worker lambdas by default, improve logging#342
Merged
Disable task cache for worker lambdas by default, improve logging#342
Conversation
… logic in tasks, add debug
…r lambda invoke command
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
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.
Workers caching their task results increases the number of dynamodb items per report run by significantly. If 1 gp function splits its work over 5 workers, then there's 5 times as many dynamodb items. The current assumption is that the parent gp function will cache their results, and therefore the worker results don't need to be cached. This will cut down on the amount of dynamodb writes.
Requirements
ToDo: