Open altaetran opened 4 years ago
To use MMseqs2 MPI you need to call mmseqs2 using mpirun
but there is no need to use MPI on a single machine. MMseqs2 will use all cores in default.
I get the same type of error when using the parallel MPI version with "RUNNER=mpirun -np 8" . I only encountered this error while testing. I ideally would like to use a cluster configuration but will not be able to if this error persists.
Expected Behavior
Providing --split-memory-limit keyword should mitigate memory requirements
Current Behavior
Works only with standard MMSeqs2 compiled version, but not with MPI compiled version.
Steps to Reproduce (for bugs)
Working on 60gb machine with 8cpus (each with 2 hyper threads) ${MMSeqs_bin}/mmseqs createDB in.fasta inDB ${MMSeqs_bin}/mmseqs cluster inDB cluDB tmp --min-seq-id 0.6 -c 0.7 -e 1e-10 --split-memory-limit 3G
Replacing {MMSeqs_bin} with {MMSeqs_non_MPI_bin} results in correct behavior without crashing
MMseqs Output (for bugs)
However, for the non MPI version, it works fine. The only difference from normal behavior is possibly the top part of these errors:
Your Environment
Version with error: aa175d63658d9aa2e908325a6fd40e9dbb260c9a-MPI Version without error: 14014cd0ec50049f796f153ea8a72164ff4b8b45
Both are self compiled on the same operating system (Debian 9 Stretch).
uname -mrs gives Linux 4.19.0-0.bpo.6-amd64 x86_64
Running on 8 core 60gb machine (with 2 hyperthreads).
Thank you!