Might be a different problem but one of our Python apps just started (half an hour ago) having very slow warmup requests that are frequently throwing DeadlineExceededError in Google code and requests that succeed are often taking 10 seconds. Seems that it is starting to get resolved now though.
On Saturday, September 21, 2013 2:29:04 PM UTC-7, Jeff Schnitzer wrote: > > Yesterday and today (and possibly longer) our (Java) app is spinning up > quite a few instances to serve simple requests. Just as one user clicking > around our site I can get GAE to spin up 4-5 instances... and many of those > requests are painfully slow warmup requests. > > It feels almost like concurrency is broken. Maybe Google is rolling out > 1.8.5 with max_concurrent_requests but accidentally picked a default of 1 > instead of the usual 10? > > One thing is that we have recently moved to maven, modules, and an ear > package (it was a very painful process, I'm sad to say). I'm not sure how > we could have done something to break the scheduler though. > > Jeff > -- 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. For more options, visit https://groups.google.com/groups/opt_out.
