Mercurial > repos > iuc > trinity
changeset 24:db1f362cca3e draft
"planemo upload for repository https://github.com/galaxyproject/tools-iuc/tree/master/tools/trinity commit f3d9db3063d2cba26e6fbe82a3eee4e1a6fe0bd5"
| author | iuc |
|---|---|
| date | Thu, 14 Nov 2019 04:06:39 -0500 |
| parents | 940901f74064 |
| children | d84caa5a98ad |
| files | README.rst |
| diffstat | 1 files changed, 9 insertions(+), 2 deletions(-) [+] |
line wrap: on
line diff
--- a/README.rst Fri Nov 01 08:11:57 2019 -0400 +++ b/README.rst Thu Nov 14 04:06:39 2019 -0500 @@ -9,7 +9,14 @@ By default, this tool is configured to limit the memory consumption to 1G. You might need to lower this limit if the machine(s) executing the jobs have less memory available. If you have a lot of reads to assemble and a machine with enough memory, you can increase it. -In both cases, you can set the GALAXY_MEMORY_MB environmental variable in the destination section of the job_conf.xml file:: + +This tool uses the GALAXY_MEMORY_MB environmental variable to limit the its memory usage. If you use a supported cluster type, you just need to limit the memory in the destination section of the job_conf.xml file to the amount of available memory (in MB), for example with a Slurm cluster:: + + <destination id="cluster_high_mem" runner="slurm + <param id="nativeSpecification">--mem=1024</param> + </destination> + +If you cluster type does not support memory limit detection, you can also set manually the GALAXY_MEMORY_MB environmental variable in the destination section of the job_conf.xml file to the amount of available memory (in MB):: <?xml version="1.0"?> <!-- A sample job config that explicitly configures job running the way it is configured by default (if there is no explicit config). --> @@ -22,7 +29,7 @@ </handlers> <destinations> <destination id="local" runner="local"> - <env id="GALAXY_MEMORY_MB">1G</env> + <env id="GALAXY_MEMORY_MB">1024</env> </destination> </destinations> </job_conf>