add option to avoid dask for large postprocessing tasks#229
Open
add option to avoid dask for large postprocessing tasks#229
Conversation
mccabete
reviewed
Aug 28, 2025
Contributor
mccabete
left a comment
There was a problem hiding this comment.
Zeb pointed out that we may need to close the client.
Contributor
|
We actually have a client.close() statement almost immediately after we call that function https://github.com/Earth-Information-System/fireatlas/blob/conus-dps/fireatlas/FireRunDaskCoordinator.py#L282. |
Collaborator
|
@eorland can you remind me of your status on this PR? Were you able to test it? I'm indeed running into the memory issue that this was intended to solve again. Thanks! |
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.
Addresses issue when memory-intensive
merge_and_save_firecall exceeds individual dask worker memory.