You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I notice that longshot is using quite a bit of memory on our PromethION (human) genomes, at the moment 140Gbyte RAM. I don't know in which step this happens, but this of course limits the number of samples I can progress in parallel on our server... I assume the suggestion is to use --region and process chromosome by chromosome, but is there a reason this cannot be implemented internally in longshot to process chromosomes separately, freeing up memory after a chromosome is done?
Let me know if this is something you could use some help with!
Wouter
The text was updated successfully, but these errors were encountered:
Hi,
I notice that longshot is using quite a bit of memory on our PromethION (human) genomes, at the moment 140Gbyte RAM. I don't know in which step this happens, but this of course limits the number of samples I can progress in parallel on our server... I assume the suggestion is to use --region and process chromosome by chromosome, but is there a reason this cannot be implemented internally in longshot to process chromosomes separately, freeing up memory after a chromosome is done?
Let me know if this is something you could use some help with!
Wouter
The text was updated successfully, but these errors were encountered: