Memory issue with test profile with --ancestry #191
Closed
AWS-crafter
started this conversation in
General
Replies: 2 comments
-
The solution here: #63 does not change the behavior. However, it works great with real genomes (not the test profile) so I think it is some quirk of the test profile. |
Beta Was this translation helpful? Give feedback.
0 replies
-
Yes, the test profile won't work well with the ancestry workflow. The ancestry workflow needs a lot more resources. Lines 17 to 20 in c4117db Setting |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
With 64 GB of RAM on Ubuntu, this occurs: "63288 MiB RAM detected; reserving 6144 MiB for main workspace," then it crashes due to not enough RAM. I think the expected behavior would be to allocate more than ~10% for main workspace.
The test profile without the --ancestry flag works fine.
Command ran: nextflow run pgsc_calc/main.nf -profile test,docker --run_ancestry pgsc_1000G_v1.tar.zst
Running with a custom.config with more RAM did not change the behavior.
Beta Was this translation helpful? Give feedback.
All reactions