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.
On Wednesday, March 27, 2013 10:08:53 AM UTC-7, notreadbyhumans wrote: > > 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-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@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.
