Assaf Gordon wrote, On 04/08/2011 10:07 AM:
> The servers processes that you should plan for are:
> 1 galaxy process for job-runner
> 2 or 3 galaxy processes for web-fronts
> 1 process of postgres
> 1 process of apache
> optionally 1 process of galaxy-reports
> you'll also want to leave some free CPUs for SSH access, CRON jobs and other
> Postgres & apache are multithreaded, but it usually balances out with light
> load on the web/DB front from galaxy (even with 30 users).
> So all in all, I'd recommend reserving 5 to 8 CPU cores to just galaxy and
> daemons (reserving means: never using those cores for galaxy jobs).
> You can do with less cores, but then response times might suffer (and it's
> annoying when you click "show saved histories" and the page takes 20 seconds
> to load...).
Forgot to mention SGE/PBS: you definitely want to use them (even if you're
using a single machine),
because the local job runner doesn't take into account multi-threaded programs
when scheduling jobs.
So another core is needed for the SGE scheduler daemons (sge_qmaster and
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: