Hello, I have a small feature request: I'd like to be able to measure the time jobs wait in "queued" state - that is - how much time passed between the job's creation and the start of execution. The reason is that I'm testing a move from the local runner to an SGE runner. I'm sure the local runner is much faster in executing (assuming there are free job threads), but the SGE runner will eventually scale better. My main concern is that because my Galaxy will compete for the SGE cluster with other users, the advantages of using the cluster will be outweighed by the wasted time the SGE jobs will be queued and not executed. Thanks, -gordon
Hi Gordon, Unfortunately, this information is not tracked right now. I've opened an issue for this request: http://bitbucket.org/galaxy/galaxy-central/issue/194/track-job-state-changes Of course, you can follow this issue if you like. Best, J. On Oct 6, 2009, at 8:38 PM, Gordon, Assaf wrote:
Hello,
I have a small feature request:
I'd like to be able to measure the time jobs wait in "queued" state - that is - how much time passed between the job's creation and the start of execution.
The reason is that I'm testing a move from the local runner to an SGE runner. I'm sure the local runner is much faster in executing (assuming there are free job threads), but the SGE runner will eventually scale better.
My main concern is that because my Galaxy will compete for the SGE cluster with other users, the advantages of using the cluster will be outweighed by the wasted time the SGE jobs will be queued and not executed.
Thanks, -gordon
_______________________________________________ galaxy-dev mailing list galaxy-dev@bx.psu.edu http://mail.bx.psu.edu/cgi-bin/mailman/listinfo/galaxy-dev
participants (2)
-
Gordon, Assaf
-
Jeremy Goecks