My graph showing ms/sec (attached) over last 24h. Average spikes were up to 32 seconds, but I think all the errors were 60+-1 sec.
On Tuesday, March 13, 2012 10:36:38 AM UTC+2, Richard Watson wrote: > > In case you're keeping track of issues thinking it's generally cleared up: > > I'm on HR and have noticed higher latencies (couple seconds instead of > e.g. 300ms) lately and sometimes higher error rates (a few instead of 0-3). > Yesterday over about 6 hours I got a ton of 60-second requests that threw > 500's with accompanying messages [1], usually on memcache sets hitting a > deadline exceeded. Also, over the last couple weeks I've been running 3 > instances permanently despite sometimes shutting them down manually. > Usually I get by on one just fine with bursts of 2 or 3. I've noticed > that one instance serves the majority of traffic with the other two serving > maybe 50 requests over many hours, so the shutdown isn't aggressive enough. > > "This request caused a new process to be started for your application..." > + > "A problem was encountered with the process that handled this request, > causing it to exit" in the same request. > > App-id: 2dumo-hr > -- 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/-/7CPSW2zXP5QJ. 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.
<<attachment: MS-per-request.png>>
