I think you want to set local_job_queue_workers instead or set the
number on the local job runner plugin element in the newer
job_conf.xml style configuration - the task runner delegates to the
underlying job runners once it has split out the tasks. The parameter
you were setting I am guessing just determines the number of threads
used to split up tasks, not run them.

-John

On Thu, Nov 7, 2013 at 9:17 AM, Jorrit Boekel
<jorrit.boe...@scilifelab.se> wrote:
> Hi list,
>
> I would need a memory refresher about tasked jobs. When testing some larger
> analyses on a local installation, I thought the local_task_queue_workers
> setting in universe_wsgi.ini would be the limiting factor for how many tasks
> can be executed at the same time. In our setup, it is currently set to 2.
> However, 5 tasks are run simultaneously, leading to memory problems.
>
> Am I overlooking something that anyone knows of?
>
> cheers,
> jorrit boekel
>
> --
> Scientific programmer
> Mass spec analysis support @ BILS
> Janne Lehtiö / Lukas Käll labs
> SciLifeLab Stockholm
>
> ___________________________________________________________
> 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:
>  http://lists.bx.psu.edu/
>
> To search Galaxy mailing lists use the unified search at:
>  http://galaxyproject.org/search/mailinglists/

___________________________________________________________
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:
  http://lists.bx.psu.edu/

To search Galaxy mailing lists use the unified search at:
  http://galaxyproject.org/search/mailinglists/

Reply via email to