Thanks for the update, but it was added in version 2.2.7 dating back to 2016 ;-) so it's not exactly "new".
Multi threading bowtie index
When building index of an organism using bowtie2-build, system is using only 1 core and less than 10% of memory(out of 64 GB) which is poor resource usage.
Is there a way to make indexing faster using bowtie2-build or how to make bowtie2 to consume more cores and memory so that indexing becomes faster?
• 4,944 views
•
link
updated
by
colindaven
•
written
by
ChillarAnand •
•
written
by
ChillarAnand •
2 answers
It's a single threaded application, there's nothing that you can do.
• 0 views
•
link
written
by
Devon Ryan
Log in to answer this question.
More posts like this
-
bowtie2-build problem to index the human genome
written by dv_f •
-
Bowtie2 index
written by aranyak111 •
-
How to index a large fasta file (>100GB) by using bowtie2-build
written by taylor •
-
"Centrifuge-build" tool - usage
written by deepak.deucy •
-
Hisat2 index building taking days even with 40 GB RAM
written by piyushjo
-
Tutorial: PBS setting combination for bismark alignment to BS-seq or RRBS data
written by Shicheng Guo
-
RAY assembler. running time/memory usage
written by Nastasiia •
-
bowtie2-build cannot use multiple cores
written by firestar
-
Bowtie2 '-P' Threads
written by fire_water
-
Tool: Sambamba: High Performance Alternative For Samtools And Picard For Indexing, Sorting And Merg…
written by William
As Devon said, there's nothing you can do about it (without rewriting the code). If you're working with a single organism with a fixed reference, it normally does not matter too much as you only need to index it once. But if you are dealing with a lot of organisms, or a lot of assemblies of the same organism, I encourage you to check out BBMap, which is multithreaded in the indexing phase and thus finishes very quickly; typically around 3 minutes for a human-size genome.
BBmap looks good. Thank you!