added GALAXY_MEMORY_MB_PER_SLOT variable#5625
Conversation
…galaxy into topic/memperslot
|
Ping @natefoo - any thoughts? Seems like an okay change to me. |
|
Yeah, seems reasonable. Just a minor request, can it be |
|
renamed it. |
|
Where could I add a bit of documentation for this? |
|
galaxy/lib/galaxy/tools/xsd/galaxy.xsd Line 2659 in 0be36ef |
|
Maybe also add some more details here: https://planemo.readthedocs.io/en/latest/writing_advanced.html#cluster-usage ? |
|
Both those places seem like good candidates. The Hub page should probably move to docs.galaxyproject.org though. |
|
@natefoo Is the docs docs.galaxyproject.org content also on github? |
|
It's generated from files in |
|
Thanks again - this good stuff and updating documentation is such a great idea (I should try that for something I do someday - meh probably not). |
When starting to use GALAXY_MEMORY_MB I realized that some tools want to know the total memory and some the memory per thread. I found it cumbersome if tool developers need to calculate that value in the tool script.
So here is my suggestion.
The two if statements may simplify the integration of statements for further cluster schedulers. Some seem to report total memory (apparently SLURM) and others per thread (UNIVA: #4857).