Hi,
I have set few jobs to run more than 24 hours ago (BWA and Tophat) but they are still flagged as "waiting to run". Is there any way to overcome this delay?
Thanks
Hi,
I have set few jobs to run more than 24 hours ago (BWA and Tophat) but they are still flagged as "waiting to run". Is there any way to overcome this delay?
Thanks
Hello,
The queue that runs mapping jobs is known to be very busy right now. Our administrator is keeping close watch over it.
The best strategy - and this is for all jobs - is to start them and then allow them to run to completion. This preserves the job placement in the queue - and is the most effective strategy for getting work done on the shared public resource at http://usegalaxy.org and likely most other Galaxy instances.
https://wiki.galaxyproject.org/Support#Dataset_status_and_how_jobs_execute
If your work is very urgent, a cloud Galaxy may be an alternative. Please see: http://usegalaxy.org/cloud
Thanks for asking! We are aware that other users are probably also curious about the delay and hopefully this helps to explain that it is known, due to a peak usage period, and how to execute work.
Jen, Galaxy team
The main public server is free to use but sometimes there is a cost in terms of time when you have to wait a day or two for work to complete. As pointed out below in the answer, many of us overcome this by running our own private Galaxy instances on dedicated hardware or on rented cloud infrastructure so our users' jobs run as quickly as possible where time is critical to their work. This is definitely the best way to avoid delay associated with heavy load on the free service.