Hi, I have been running a raxml-ng tree construction for about 18 hours now on our lab "server" computer.
I wasn't sure how many bootstraps to do, so I ran the following command:
(I used modeltest-ng to identify the "ideal" a.a. substitution model)
RAxML-NG v. 1.0.1 released on 19.09.2020 by The Exelixis Lab.
Developed by: Alexey M. Kozlov and Alexandros Stamatakis.
Contributors: Diego Darriba, Tomas Flouri, Benoit Morel, Sarah Lutteropp, Ben Bettisworth.
Latest version: https://github.com/amkozlov/raxml-ng
Questions/problems/suggestions? Please visit: https://groups.google.com/forum/#!forum/raxml
[00:00:00] Generating 10 random starting tree(s) with 1107 taxa
[00:00:00] Generating 10 parsimony starting tree(s) with 1107 taxa
[00:00:19] Data distribution: max. partitions/sites/weight per thread: 1 / 229 / 18320
[00:00:21] Data distribution: max. searches per worker: 86
Starting ML tree search with 20 distinct starting trees
I don't really understand threading vs core performance in reference to software optimizations, so I didn't specify & and let the software decide on it's own. But reading through some issues others have had, incorrectly specifying core/thread count leads to a severe attenuation of the software performance?
Of course, I can run the tree construction with say 100 bootstraps or subsetting data (and I likely will, just to make sure everything else is going OK), but does this lengthy time frame seem consistent with the fasta file I have inputted (descriptions of the fasta file are provided in the log I have described above)?
Edit:
Apologies for creating this "issue", the log just printed:
[17:17:59] [worker #10] ML tree search #11, logLikelihood: -302170.878412
Perhaps I perform tree construction on a cluster instead of our struggling computer.
Closing this issue.
Hi, I have been running a raxml-ng tree construction for about 18 hours now on our lab "server" computer. I wasn't sure how many bootstraps to do, so I ran the following command:
(I used modeltest-ng to identify the "ideal" a.a. substitution model)
raxml-ng -all --msa new_alignment_file2.fasta --model JTT+I+G4 --bs-trees autoMRE
The log file is currently reading:
I don't really understand threading vs core performance in reference to software optimizations, so I didn't specify & and let the software decide on it's own. But reading through some issues others have had, incorrectly specifying core/thread count leads to a severe attenuation of the software performance?
Of course, I can run the tree construction with say 100 bootstraps or subsetting data (and I likely will, just to make sure everything else is going OK), but does this lengthy time frame seem consistent with the fasta file I have inputted (descriptions of the fasta file are provided in the log I have described above)?
Edit: Apologies for creating this "issue", the log just printed:
Perhaps I perform tree construction on a cluster instead of our struggling computer. Closing this issue.