feat(aws-healthomics): add steering for CPU/GPU resource fallback via… - #193
Open
alxawan wants to merge 1 commit into
Open
feat(aws-healthomics): add steering for CPU/GPU resource fallback via…#193alxawan wants to merge 1 commit into
alxawan wants to merge 1 commit into
Conversation
… the omicsResourceFallbackOrder directive
markjschreiber
suggested changes
Sep 1, 2026
| - `docker` and `maxRetries` are shared, not per-profile — set them once at the top level as | ||
| you would for any other task. See the [Workflow Development SOP](./workflow-development.md#task-parameters). | ||
|
|
||
| ## Example |
Contributor
There was a problem hiding this comment.
Can you add equivalent Nextflow and CWL examples if these are supported
| - A value as low as 1 minute is accepted, but only allows roughly one capacity-search cycle | ||
| before advancing — this is USUALLY too aggressive for anything but a deliberately fast | ||
| first-choice profile. | ||
| - For scarce accelerator types (e.g. `nvidia-l40s`), RECOMMEND >= 20 minutes so the profile |
Contributor
There was a problem hiding this comment.
How would an agent know what is scarce? At any given time any GPU could be relatively plentiful or scarce? It will also depend on the region. Some regions/ AZs only have newer GPU types and these might not be scarce in those regions?
| - For scarce accelerator types (e.g. `nvidia-l40s`), RECOMMEND >= 20 minutes so the profile | ||
| gets a fair chance before advancing (see rule 9 above). | ||
| - The sum of every profile's wait window SHOULD stay well under the run's overall timeout | ||
| (maximum 7 days) — a long fallback list with generous per-profile timeouts can otherwise |
Contributor
There was a problem hiding this comment.
Default maximum is 7 days.
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
2 participants
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.
feat(aws-healthomics): add steering for CPU/GPU resource fallback via…
omicsResourceFallbackOrder, a new workflow directive.By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.