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

bwa and bwa-mem2 relative indexing memory usage #255

Open
ImagoXV opened this issue Jan 25, 2024 · 2 comments
Open

bwa and bwa-mem2 relative indexing memory usage #255

ImagoXV opened this issue Jan 25, 2024 · 2 comments

Comments

@ImagoXV
Copy link

ImagoXV commented Jan 25, 2024

Hi there, there is something I find rather strange between bwa and bwa-mem2

bwa-mem2 is supposed to be faster and more memory efficient than bwa.

However, I cannot index SILVA 138.1 on my 32Gb 12cores with bwa-mem2 because of memory overusage. But I don't have any issue with bwa (expect, for sure, that it is really long).

I usually index on my cluster so memory is not that much of a problem. But for this particular application, I need it to be doable on a regular powerful laptop.

Maybe there is something I don't understand correctly, or maybe I'm not using bwa-mem2 index correctly

bwa-mem2 index -p SILVA_IDX SILVA_138.1_SSURef_tax_silva.fasta.gz

Kills my computer

bwa index -p SILVA_IDX SILVA_138.1_SSURef_tax_silva.fasta.gz

Runs smoothly.

Thanks for the discussion.

Arthur

@slw287r
Copy link

slw287r commented Jan 30, 2024

Peak memory ~72G building the index on our HPC:

bwa-mem2 index SILVA_138_SSURef_tax_silva.fasta.gz

189371

@ImagoXV
Copy link
Author

ImagoXV commented Jan 30, 2024

Yeah where bwa is max ~30Gb

Anyone know what are the discrepencies in indexing algorithm making so much difference ?

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