Delayed execution of tasks in 1.7.6.

[notreadbyhumans]

I've noticed that since updating a live app to 1.7.6 new tasks are sitting in named task queues for up to a couple of minutes before executing. The queues are empty (no executing tasks) and have ample execution rates (20/s) and bucket sizes (30), and tasks can be manually run.

Has anyone else experienced similar issues?

[Moises Belchin]

Me too.

Saludos.

Moisés Belchín.

2013/3/27 notreadbyhumans <notread...@gmail.com>

I've noticed that since updating a live app to 1.7.6 new tasks are sitting in named task queues for up to a couple of minutes before executing. The queues are empty (no executing tasks) and have ample execution rates (20/s) and bucket sizes (30), and tasks can be manually run.

Has anyone else experienced similar issues?

--
You received this message because you are subscribed to the Google Groups "Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-appengi...@googlegroups.com.
To post to this group, send email to google-a...@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[stevep]

Yes. Very noticeable in some situations where an instance absolutely has tons of cpu cycles going to waste and yet taskqueue crickets are heard chirping. Why??? Having pondered this, unpredictable TQ starts is a very, very old source of complaints. One must be resigned to it I guess.

[notreadbyhumans]

Oddly I've just run the same tests a day later and responsiveness is back to where I would expect it i.e. queues with large rates and buckets clear before you have a chance to reload the console page.

Hopefully the App Engine team are tracking this as - instance resources allowing - we need to be able to rely on rapid task execution.