3.9 years ago by
United States
I assume you haven't configured a job manager like SLURM or Torque (https://wiki.galaxyproject.org/Admin/Config/Performance/ProductionServer)? These can help take advantage of large resources like this.
Even if you don't want to set up something like that - Galaxy can be configured to take advantage of more cores but it won't attempt to do much intelligent automatically. There is some discussion here - C: GALAXY_SLOTS not working.
For your setup I might setup a config/job_conf.xml file like the following:
<job_conf>
<plugins>
<plugin id="local" type="runner" load="galaxy.jobs.runners.local:LocalJobRunner" workers="8"/>
<plugin id="multilocal" type="runner" load="galaxy.jobs.runners.local:LocalJobRunner" workers="2"/>
</plugins>
<handlers>
<handler id="main" />
</handlers>
<destinations default="local">
<destination id="local" runner="local"/>
<destination id="multicore8" runner="multilocal">
<param id="local_slots">8</param>
</destination>
</destinations>
<tools>
<tool id="bowtie2" destination="multicore8" />
<tool id="bowtie" destination="multicore8" />
<tool id="deeptools" destination="multicore8" />
<tool id="cufflinks" destination="multicore8" />
<tool id="cuffdiff" destination="multicore8" />
<tool id="cuffmerge" destination="multicore8" />
<tool id="tophat2" destination="multicore8" />
</tools>
</job_conf>
This will allow 8 single core jobs to run simultaneously and will reserve the other 16 cores to run two 8 core jobs and assigns bowtie2, bowtie, cufflinks, etc.... to run in these multi-core slots.
I hope this helps.
Update: Adjusted XML snippet to remove incorrect, extraneous attributes.
Update 2: Added missing handlers tag preventing this file from loading.
•
link
modified 3.3 years ago
•
written
3.9 years ago by
jmchilton ♦ 1.1k