cloud: Bump archival RAM to (the max of) 8GB #615
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
Bump the RAM allocated to the data archival cloud function from 4GB to 8GB, so we avoid aborting on out-of-memory when transferring 12 hours of data at a time. It could be that BigQuery is accumulating memory use over time and running out, despite us calling gc.collect() after every transfer, but I don't have the time to pursue this further.
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.
Bump the RAM allocated to the data archival cloud function from 4GB to 8GB, so we avoid aborting on out-of-memory when transferring 12 hours of data at a time.
It could be that BigQuery is accumulating memory use over time and running out, despite us calling gc.collect() after every transfer, but I don't have the time to pursue this further.