Hi Manni, It sounds like 1 of 2 things is happening:
1. Queue depth is not accurate. We are actively working on improving the accuracy of this number (it's a really hard problem to solve!) 2. You may have tasks scheduled to run in the future (either intentionally or because they are being retried) If you want to email me your application ID and queue name, we could dig in and see what's going on. [email protected] -Kim App Engine, Product Manager On Thursday, April 28, 2016 at 10:45:49 AM UTC-7, Manuele Cavalli-Sforza wrote: > > I have a push queue with a number of long running tasks enqueued. I notice > that the push queue has reached a state, however, where the No. of running > tasks < No. of tasks in queue < Max number of concurrent tasks. > > This is unideal, as I would like the queue to be processing at its maximum > capacity. Does this have to do with the bucket size set on the queue? Would > tweaking this alter the queue's responsiveness? > > It is also relevant to note that I updated the queue configuration, after > adding the tasks, to be a max of 40 concurrent tasks. Also, I added the > tasks all at the same time. I noticed that the queue initially processed > the tasks well at the original 20 concurrent task limit, but -- when > updated to 40 concurrent tasks -- did not seem to respond, and always kept > a task running number of under 20. Any insights from other users' > experience or the Google team? > > Thanks, > > Manni > -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/487e706e-e5ee-4a4d-92d6-c82039edd909%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
