Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[EchoCallset] Retry with more memory VCF extract [VS-1351] #8814

Merged

Conversation

mcovarr
Copy link
Collaborator

@mcovarr mcovarr commented May 6, 2024

No description provided.

@mcovarr mcovarr requested review from RoriCremer, rsasch and gbggrant and removed request for RoriCremer and rsasch May 6, 2024 17:03
@mcovarr mcovarr force-pushed the vs_1351_retry_with_more_memory_vcf_extract_echo_callset branch from 910d7d3 to 88ebd90 Compare May 6, 2024 23:24
@mcovarr mcovarr changed the title Retry with more memory VCF extract EchoCallset edition [VS-1351] [EchoCallset] Retry with more memory VCF extract [VS-1351] May 6, 2024
@mcovarr mcovarr marked this pull request as ready for review May 6, 2024 23:25
Copy link

@rsasch rsasch left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

link to test run?

exit 1
fi

gatk --java-options "-Xmx${memory_mb}m" \
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

oooooh i didn't know we could do this!
(can we do this all over the VAT pipeline too!??!?!)

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sure why not. The hard part is remembering to tick the 'Retry with more memory' option when launching the workflow lol

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

And we already need to remember to click on the reference disk checkbox for that...

@mcovarr
Copy link
Collaborator Author

mcovarr commented May 7, 2024

Intentionally failing test run here where I sabotaged the code to simulate an out of memory condition. You can see on the first attempt memory usage looks like

echo 'MEM_SIZE: 40.0, MEM_UNIT: GB, memory_mb: 37000, memory_gib: 40'

after three retry-with-more-memory retries, things look like:

echo 'MEM_SIZE: 69.12, MEM_UNIT: GB, memory_mb: 66120, memory_gib: 40'

@mcovarr mcovarr merged commit d801f5e into EchoCallset May 7, 2024
17 checks passed
@mcovarr mcovarr deleted the vs_1351_retry_with_more_memory_vcf_extract_echo_callset branch May 7, 2024 19:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants