Hi Thon
Have you made any progress regarding the delays you've experienced?
I had some time this morning and was digging in the code a little
bitin '~/lib/galaxy/jobs/manager.py' there is on line 155:
time.sleep( 5 )
and I am wondering is this delay really necessary? - needless to s
On Oct 23, 2012, at 12:55 PM, Anthonius deBoer wrote:
> I created the index but that did not change anything...
> I had sent James Taylor the schema as he requested, but I never heard
> anything so I guess he must not have found anything weird...
>
> I am waiting to move my Galaxy server off to
On Tue, Oct 23, 2012 at 12:55 PM, Anthonius deBoer wrote:
> I had sent James Taylor the schema as he requested, but I never heard
> anything so I guess he must not have found anything weird
Yes, it appears to have all the right indexes to me.
__
I created the index but that did not change anything...
I had sent James Taylor the schema as he requested, but I never heard anything
so I guess he must not have found anything weird...
I am waiting to move my Galaxy server off to a three server configuration, so I
am hoping the problem will no
Hi Thon
Sorry for re-activating an old e-mail thread. I am just curious, whether
Nate's suggestion solved your problem?
After our upgrade (from the "March 12th changeset 6799:40f1816d6857" to
the "October 5th changeset 7824:b5bda7a5c345") we see long delays in the
jobs going from queued to
On Sep 18, 2012, at 6:31 PM, Anthonius deBoer wrote:
> Hi,
>
> Jobs that I start on my in-house Galaxy instance now take up to 3-4 min to go
> from queued to Running, even though there is nothing much going on on the
> galaxy server...
>
> I have been running this instance since June and use a
Hi,Jobs that I start on my in-house Galaxy instance now take up to 3-4 min to go from queued to Running, even though there is nothing much going on on the galaxy server...I have been running this instance since June and use a relatively new version of Galaxy-central (Last update, 22-Aug changeset:
