Hi Ted
You can cut down the lag by 5 secs if you delete the "time.sleep( 5 )"
in '~/lib/galaxy/jobs/manager.py' ( line 155)
(see also my e-mail from Nov 7: in this email conversation:
http://dev.list.galaxyproject.org/Jobs-are-slow-to-start-on-my-galaxy-instance-Used-to-be-much-faster-tt4656337.html
There has been a follow up discussion on the IRC Channel: as it turns
out, this time delay is necessary for certain users, depending on their
set-up - Hence be careful, when deleting it.
Regards, Hans-Rudolf
On 12/04/2012 04:19 PM, Ted Goldstein (PhD candidate) wrote:
This Galaxy speed and production question reminded me that I have been meaning
to raise the following question on the list:
For a single job (workflow item), It seems like there is a 20 second lag
before the job is launched. It gives the impression that Galaxy is slow and
unresponsive (in the sports car sense). I imagine that it is a combination of
python's poor thread architecture and web polling latency. Has anyone looked
into the latency of running a process?
Ted
___________________________________________________________
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/
