Question

Blastclust Ignores The Multithreading Argument (-A)

2

Entering edit mode

13.6 years ago

Aleksandr Levchuk 3.2k

I'm trying to run:

blastclust -a 48 -p T -d ./uniprot/2011_04/all.fasta  -v progress

I have 48 cores on the server thus -a 48 argument, but only 100% CPU (1 core) is used.

I have Blast2 version 2.2.21 (standard for Debian 6).

This seems to be a bug because parallelism is clearly requested and at least a warning message should be show when proceeding on a single core.

Does anyone know how to workaround this?

blast parallel clustering • 3.8k views

ADD COMMENT • link updated 12.6 years ago by Hamish ★ 3.3k • written 13.6 years ago by Aleksandr Levchuk 3.2k

2

Entering edit mode

It is probably not compiled with pthreads support - but that is hard to tell without further investigation. However, consider using Uclust or CD-HIT instead.

ADD REPLY • link 13.5 years ago by Martin A Hansen 3.0k

0

Entering edit mode

Do the -a switch work for regular blast?

ADD REPLY • link 13.5 years ago by Martin A Hansen 3.0k

0

Entering edit mode

Yes. blastall -a 7 -p blastp -i ~/myseq.fasta -d ./uniprot/2011_04/all.fasta got only up to 130% CPU on the first run. And 700% on the second identical run.

ADD REPLY • link 13.5 years ago by Aleksandr Levchuk 3.2k

0

Entering edit mode

Did you manage to resolve this problem?

ADD REPLY • link 12.9 years ago by Sequer ▴ 150

0

Entering edit mode

No. Looks like not a lot of people liked this question. An nobody even tried a simple repro.

ADD REPLY • link 12.9 years ago by Aleksandr Levchuk 3.2k

Ram · Answer 1 · 2012-02-15

From a little experimentation I can tell you that 'blastclust' is multi-threaded, but only when it come to the cluster generation part. The initial preparation, i.e. before the "Start clustering of NNNN queries" message is single threaded.

You can check that the process is using threads by using 'ps', from the man page:

To get info about threads:

ps -eLf
ps axms

Which for a sample case, clustering PDB proteins using four threads, shows the expected number of threads:

hamish    2141  1455  2141 20    5 21:40 pts/0    00:01:05 blastclust -i pdbaa -a 4 -o outfile.txt
hamish    2141  1455  4232  0    5 21:45 pts/0    00:00:00 blastclust -i pdbaa -a 4 -o outfile.txt
hamish    2141  1455  4233  0    5 21:45 pts/0    00:00:00 blastclust -i pdbaa -a 4 -o outfile.txt
hamish    2141  1455  4234  0    5 21:45 pts/0    00:00:00 blastclust -i pdbaa -a 4 -o outfile.txt
hamish    2141  1455  4235  0    5 21:45 pts/0    00:00:00 blastclust -i pdbaa -a 4 -o outfile.txt
hamish    4236  1610  4236  0    1 21:45 pts/1    00:00:00 ps -eLf

This is on Ubuntu 10.04 LTS, which uses the Debian supplied NCBI BLAST 2.2.21 which you mention. So I'm guessing that you were unlucky enough to be looking at the wrong moment, when it appears to be single threaded.