Tasks aren't guaranteed to execute immediately. Task queues execute when there is capacity: http://code.google.com/appengine/docs/python/taskqueue/overview.html#Task_Execution
It may or may not be related to 1.3.1. What % of your requests see this delay? On Thu, Feb 25, 2010 at 3:05 PM, Jerome <[email protected]> wrote: > Hello, > > We have been using task queues for a few months without problem. We > handle actions that must execute right away. > > At the time of the release of 1.3.1, we noticed that sometimes, some > tasks will take 1 to 2 minutes to start, but in the task queue, the > ETA shows as a date in the past (like 0:01:12 ago), usually 1 second > or so after the creation time. > > This is not a consistent issue. I might works perfectly (task being > kicked in within 1 second of creation) for several times and suddenly, > the next task takes 1.5 minutes to get started. > > Our task queue is empty when we see this issue. > Our queue is setup with a max rate of 5/s and a bucket size of 1. > > Any idea of what we can do to work around or solve this new issue? > > Jerome > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine for Java" group. > To post to this group, send email to > [email protected]. > To unsubscribe from this group, send email to > [email protected]<google-appengine-java%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/google-appengine-java?hl=en. > > -- Ikai Lan Developer Programs Engineer, Google App Engine http://googleappengine.blogspot.com | http://twitter.com/app_engine -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
