The system seems to be returning to normal after 60 hours of 60,000 - 120,000 ms latency in taskqueue execution instead of 60 - 120 ms.
I am surprised users were not more vocal about this and no acknowledgement / explanation from Google. Maybe people don't use taskqueues the way I use them - process some data on a taskqueue and then push it back to the UI. For this period of increased latency my users were getting their asynchronous data back in the UI one to two minutes after they had submitted it instead of the usual less than two seconds. I imagine App Engine uses taskqueues as a way of smoothing out server traffic as they can stack them when load is high and run them when it is low and for the last 60 hours load has been continually high... On Monday, November 12, 2012 12:00:19 PM UTC, Marcel Manz wrote: > > Can someone from Google please respond to this issue? > > The execution latency issue exists now for more than 48 hours and still no > word or alerts about it. Can Google please allocate more human resources in > order to communicate better? This is a business oriented service and such > lack of communication must just not happen. And we don't care if such > issues happen on weekends, App Engine needs to be stable 24/7. > > - Marcel > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/zlYWQaOKJVEJ. 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?hl=en.
