mpiblast
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
mpiblast [2010/01/18 08:03] – 172.26.0.166 | mpiblast [2010/01/18 12:15] – 172.26.0.166 | ||
---|---|---|---|
Line 3: | Line 3: | ||
http:// | http:// | ||
+ | |||
+ | < | ||
* **--nfrags=10** Specifies how many database fragments you want to split the original database into. This should be equal to how many different nodes you want to run mpiblast on. | * **--nfrags=10** Specifies how many database fragments you want to split the original database into. This should be equal to how many different nodes you want to run mpiblast on. | ||
Line 30: | Line 32: | ||
===== wwwblast ===== | ===== wwwblast ===== | ||
http:// | http:// | ||
+ | |||
+ | |||
+ | ===== Frequently Asked Questions ===== | ||
+ | Collection of the more-helpful questions and answers from the [[http:// | ||
+ | ====How do I format a huge database? | ||
+ | |||
+ | Large databases like nt can consume several gigabytes of disk space and it is preferable to store them in compressed form. Starting with mpiBLAST 1.4.0 it is possible to pipe FastA formatted sequence data into mpiformatdb. This feature provides the ability to directly format a compressed (gzip/bzip etc.) database using command line syntax like: | ||
+ | < | ||
+ | ===== Benchmarks ===== | ||
+ | < | ||
+ | | ||
+ | real 7m48.052s | ||
+ | user 7m40.775s | ||
+ | sys | ||
+ | |||
+ | < | ||
+ | Total Execution Time: 395.754 | ||
+ | |||
+ | real 6m36.841s | ||
+ | user 12m13.891s | ||
+ | sys |