-
Notifications
You must be signed in to change notification settings - Fork 55
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
Add SLURM support #215
Comments
Hi |
Many thanks @TSL-RamKrishna - that's great! As it happens I've just got access to a SLURM cluster, so I can actually try this out. |
Thanks. Let me know when you try that out. I have push updated the repo today as well. |
The changes have now been pulled into @all-contributors please add @TSL-RamKrishna for code, ideas |
I've put up a pull request to add @TSL-RamKrishna! 🎉 |
Is the branch https://github.com/widdowquinn/pyani/tree/pr_236 still in progress and the best bet if I urgently needed to run pyANI under SLURM? Is it worth making that into a new pull request to garner feedback on? |
Tagging @widdowquinn to make sure he sees this sooner. |
It is still in progress. The current status is that the The usual setting of the maximum number of submittable jobs on a SLURM cluster is not much higher than this, which greatly limits the potential for scaling on a SLURM cluster. The changes required to how we handle jobs in the backend are significant and probably best handled in concert with other changes we have planned. It's a much bigger job than just a drop-in replacement for the old SGE code. |
Thanks. I suspected the SLURM batching was still an issue from our discussion elsewhere. I'm hoping to use this on up to 500 genomes, so would hit this problem :( |
Aye - I need to make progress on this for my own stuff, but this time of year is unpleasantly busy. |
Summary:
pyani
currently only supports SGE/OGE-like systems, but SLURM is very popular. It would be useful to support SLURM scheduling.The text was updated successfully, but these errors were encountered: