Update to Parsl docs for Polaris #258
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
|
Is there something I could do to move this PR forward? |
felker
reviewed
Aug 23, 2023
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.
Recent changes to the Parsl code base made the sample Parsl config in our docs for Polaris un-runnable (see: Parsl/parsl#2828).
Also, there have been improvements added to Parsl in the past 12 months that make the use of Parsl on Polaris better (for example, the use of
spawnrather thanforkwhen using the python multiprocessing library to create new processes on a node and an option for reversing the order of hardware threads relative to GPUs that Parsl assigns). These improvements have now been added to the sample config.