Yes I got that too, shortly after the maintenance period ended, I dont seem to get them anymore though.
During maintenance I got some huge CPU time per request readings - which I guess is understandable?. However, I simply cannot see how my resource consistently uses nearly double the the CPU time it did before the maintenance. Unless the changes they made were to make requests more expensive ;) On 14 Sep, 10:31, Tonny <12br...@gmail.com> wrote: > I get a general 500 error for an app. Same source as yesterday - so > would say it's not a coincidence. > > This message appears in the log: > Request was aborted after waiting too long to attempt to service your > request. This may happen sporadically when the App Engine serving > cluster is under unexpectedly high or uneven load. If you see this > message frequently, please contact the App Engine team. > > On Sep 14, 11:14 am, mscwd01 <mscw...@gmail.com> wrote: > > > Hey, > > > This may just be a coincidence but my average CPU time per request has > > risen noticably since yesterdays maintenance. Whereas my average was > > 250-300ms, it now takes on average 500-600ms. This is the exact same > > resource without any changes made, so I cannot seem to work out why > > this would be. Has anyone else noticed this? > > > 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 google-appeng...@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
