On 08/24/2012 05:22 PM, kauerb...@comcast.net wrote:
Hello,

On our local instance of Galaxy jobs are taking an extremely long time
to run, or they are not run at all. In the history it always says "job
is waiting to run", even simple jobs like reformatting text files to be
tab delimited. Is there a way to 1) check the Galaxy job queue, and 2)
perhaps modify some parameters to speed up processing?

Any suggestions would be greatly appreciated.


Hi Kenneth

Usually, Galaxy is not slow, but the tools executed by Galaxy are slow (eg due to bad IO performance of the host server).

"job is waiting to run" indicates there are unfinished jobs in the queue. There are two ways to check the queue:

If you are an 'Admin', select the Admin tab -> "Manage jobs". This will list all running jobs. And you can kill jobs as well.

Or use the galaxy report tools and have a look at "Today's jobs"



Depending on your set-up, you might consider changing "universe_wsgi.ini":

   # Number of concurrent jobs to run (local job runner)
   local_job_queue_workers = 5

to allow more parallel jobs



Hope this helps
Hans



Thank you.




___________________________________________________________
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/

___________________________________________________________
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/

Reply via email to