I could use a little bit of help in making some changes to our galaxy server.
I'm in the process of setting up/testing a production galaxy server for our
research computing center. Our server is setup with an apache proxy, ldap
authentication and jobs will run as the logged in user.
The server running galaxy has 24 cores. While most of the jobs submitted will
go to either our HPC or the condor cluster there are some jobs that are small
and should run on the galaxy server itself.
I was planning to set up a single web handler and 23 job handlers. I don't
expect the web server to get bogged down, especially since I have apache
serving as a proxy.
I expect a smaller (<100) number of users submitting many jobs.
I just went with 23 handlers for no good reason other than the server has 24
cores. Perhaps there is a better way to discern the optimum number of job
I'd like jobs submitted to galaxy to go either to our HPC, Condor, or one of
the 23 local workers. Can galaxy effectively load balance itself in this way?
Does the configuration below accomplish this?
use = egg:Paste#http
port = 8081
host = 127.0.0.1
use_threadpool = true
threadpool_workers = 10
<plugin id="local" type="runner"
<plugin id="drmaa" type="runner"
<destination id="local" runner="local" tags="head"/>
<destination id="dynamic" runner="dynamic">
<destination id="moab" runner="drmaa" />
<destination id="local" runner="local" />
In my destinations.py script I point tools to the appropriate destination:
return JobDestination(id="local", runner="local")
Please keep all replies on the list by using "reply all"
in your mail client. To manage your subscriptions to this
and other Galaxy lists, please use the interface at:
To search Galaxy mailing lists use the unified search at: