-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove clustalw, set fixed raxml memory #72
Conversation
I have very few "ok" clustalw jobs with inputs over 60 MB. |
|
|
On AU, for clustalw:
|
For latest raxml:
This gxadmin query/filter combo is extremely neat. Thanks for this @natefoo! clustalw settings here probably came from AU and may not have changed since dtd days. |
I am not sure what is going on here but:
In practice on .org the histogram looks like:
Maybe old versions were much more inefficient? But it does not seem like we need to allocate anything special for the current version. I would be interested to see what memory usage looks like at EU and AU.
Also with larger inputs the tool runs forever, AU rejects anything >= 40 MB, I will update if I can determine what the rough size at which it runs forever for us is, and maybe it is worth including that in the shared DB?
raxml wants 16 cores but because of the memory factor that most people use in their default tool (see #73) is probably going to also request ~64 GB of memory despite only using ~2 GB: