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

Basevar needs a lot of memory to run successfully #14

Open
thanhtruc44 opened this issue Jul 30, 2024 · 1 comment
Open

Basevar needs a lot of memory to run successfully #14

thanhtruc44 opened this issue Jul 30, 2024 · 1 comment

Comments

@thanhtruc44
Copy link

Dear author,

I have used Basevar on 5 BAM files, each approximately 3GB in size, but it requires a substantial amount of memory to run successfully, specifically up to 200GB. I would like to know if I am operating it correctly. The command I used is as follows:

basevar basetype  -R "reference/GCA_000003025.6_Sscrofa11.1_genomic.fa" 
-I SRR14775051_Capture.dedup.bam -I SRR14775062_Capture.dedup.bam 
-I SRR14775073_Capture.dedup.bam -I SRR14775074_Capture.dedup.bam 
-I SRR14775085_Capture.dedup.bam  --batch-count 50 --filename-has-samplename  
--output-vcf "pig.vcf.gz"   --output-cvg "pig.cvg.tsv.gz" --nCPU 32
@ShujiaHuang
Copy link
Owner

ShujiaHuang commented Sep 11, 2024

Hi, thanks for your information. I've totally fix these issues by using C++ to reconstruct the whole codes of basevar.
I recommend utilizing the C++ version directly, which can be accessed at : https://github.com/ShujiaHuang/basevar.

In this updated version, each thread (-t/--thread) typically necessitates only 3GB to 4GB of memory if the -B (--batch-count) parameter is set to 200. I anticipate that for your specific scenario, the memory requirement might be less than 10GB.

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

No branches or pull requests

2 participants