Casper resource updates and some recommendations for Derecho #119
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
|
This has a lot of overlap with #118 . So I will close this and make another PR to that branch. vanderwb:system-updates |
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.
Here are some better resource selection for ncar cluster that will fix some issues, especially on Casper.
First 4GB workers is more appropriate on Casper. I have added some other Casper-relevant and PBS relevant options for Casper so the jobs will not be held in the queue.
For Derecho: Running dak workflows on Derecho should be avoided but Derecho now has a shared queue that can be possibly more useful for some development workflows.