Someone in Google has tried turning it on and off again. Things are really flying now.
I would just ask Google to stop with the standard "We have determined that this spike did not affect the performance or uptime of applications." Please change that default message to something a little more vague and less insulting. Thanks! On Sep 14, 10:48 pm, Kenneth <[email protected]> wrote: > Now the status site is just returning a blank page and the rate of 500 > errors has gone up significantly. > > I can't believe that downtime notice thinks this issue is over. My > app is barely usable. > > Come on Google, give us something better. At least let us know you > know there's an ongoing serious problem. > > On Sep 14, 8:16 pm, Michael Robellard <[email protected]> wrote: > > > > > > > > > I am seeing thousands of errors(all timeouts of one type or another) > > on requests that typically have less than 100 errors a day. My CPU > > usage per second is up 20% since the failure this morning. These are > > requests that usually take less than a second and they are reaching > > the 30 second mark. > > > On Sep 14, 3:04 pm, mscwd01 <[email protected]> wrote: > > > > Hi, > > > > Can we get an official word on why the App Engine has performed so > > > poorly today? > > > > My app has seen hundreds of HTTP 500 errors, is running approximately > > > twice as slow (CPU time/request) as yesterday (PUTs are very slow), > > > had many "HardDeadlineExceededError" errors and stats tools such as > > > AppStats don't appear to be working for me (displays "real" time but > > > not cpu time). > > > > It'd be reassuring to know why these problems are occurring and what > > > is being done to fix these and stop the happening again. > > > > Thanks -- You received this message because you are subscribed to the Google Groups "Google App Engine" 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?hl=en.
