On Apr 8, 2011, at 11:01 AM, Dave Walton wrote:
This is very close to our config, except -
We run all of this on a 4 core Virtual Machine running SUSE Linux Enterprise
Server 11 (x86_64) with 16 GB of memory.
Instead of SGE our HPC cluster uses Torque/Moab for scheduling.
Also, we've
On 04/07/2011 11:40 PM, Ryan Golhar wrote:
Hi all - So, I been asked to provide specs for a production Galaxy
system to support approximately 20-30 users. Most of these users are new
to bioinformatics and very new to NGS. I'm targeting a user base that
will use a light to moderate amount of
Assaf Gordon wrote, On 04/08/2011 10:07 AM:
Processes:
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
Assaf Gordon wrote:
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
On Fri, Apr 8, 2011 at 10:26 AM, Nate Coraor n...@bx.psu.edu wrote:
Assaf Gordon wrote:
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.
This is very close to our config, except -
We run all of this on a 4 core Virtual Machine running SUSE Linux Enterprise
Server 11 (x86_64) with 16 GB of memory.
Instead of SGE our HPC cluster uses Torque/Moab for scheduling.
Also, we've set up a separate IO Node for upload of data files from the
