Closed
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.
Ran stormhub for the Allegheny watershed and ran into some memory issues even when using an AWS EC2 with 100GB of RAM.
The issue was the script for generating the storm catalog kept getting killed due to OOM. The root cause of this was during the item creation where each item is saved to disk and then appended to the collection. The edit instead only saves to disk and returns None. Afterwards the items are added to the catalog by referencing memory on disk rather than memory in RAM.
The only relevant changes in the PR that should be merged are in the storm_catlog.py file.