Issue 1695 is the highest non-acknowledged Defect, soon to be the highest non-acknowledged issue, and the only non-acknowledged defect in the top 100 issues.
I'm (really) not upset about the bug (though it is definitely causing our users, and therefore us, grief), but I am definitely becoming increasingly frustrated by the lack of acknowledgement. Google - if there is something we the community can help with, please let us know! j On Sep 24, 7:03 pm, Tim Hoffman <[email protected]> wrote: > Hi > > I will start out and say I think app engine is great, I am doing a lot > of work with it and I do think some of the criticsm to date has been a > tad harsh. > > However I am at a bit of a loss the reconcile the typical messages in > the System Status log and reality > for instance > > 08:36 AM Python > > Investigation Complete - Issue Resolved > We have determined that this spike did not affect the performance or > uptime of applications. If you feel we have incorrectly diagnosed this > issue please inform us by posting in our developer forum. > > However for more than several minutes multiple applications that I > have running on app engine where all exhibiting > <class 'google.appengine.runtime.DeadlineExceededError'>: and > presenting Error 500 pages to the end user. > > This occurred for several periods between 5:33AM (some time in the US) > to 8:30AM for several minutes at a time. > > All of these where during app startup on what is essentially a read > only site (i.e. writes to the datastore rarely happen) > > Now it begs the question what does "We have determined that this spike > did not affect the performance or uptime of applications" mean in > these circumstances. How long do apps have to be affected before it > would be classed an outage, or how many different apps would need to > be affected. > > In addition I would like to suggest that the system status monitoring > tasks include an app that is measuring the startup of something a > little more complex than a simple handler. For instance starting up a > typical DJango stack (I don't use django myself) or something similiar > that under normal running will typically take 4-6 secs to startup. > These are the types of instances that seem to be heavily affected by > the type of outage I experienced and apps built on it are not unusual. > > I personally take steps to guard against slow startup and have a fast > startup path if I can server the page out of cache, which means I can > startup an instance in around 10ms if the page is in memcache, or 4-10 > secs typically if not. Where I am blowing up at the moment is that > 4-10 secs startup time is blowing out to 30sec and deadline exceeded. > Given that 99% of the time I can startup a complex stack reliably in < > 10sec, means these occurances would have to be considered unusual. > > I have starred > Issuehttp://code.google.com/p/googleappengine/issues/detail?id=1695 > (and in fact many people have ). There also seems to be an increasing > amount of frustration about this issue as there hasn't really been (at > least that I have seen) any recognition from Google that a problem > exists and that it is being looked into (however I am sure it is, just > we don't get much feedback on it). > > Some outcomes I personally would like to see would be > > 1. Clarification of what constitutes an outage, or improved > descriptions of the problems in System Status > 2. Some recognition of what does seem to be an ongoing problem. > 3. A more complex app startup test in the system status. > > Thank you for your time and (what I consider to be a ) refreshing and > exciting deployment and development platform. > > Thanks > > Tim Hoffman > > P.S. Excuse typos and poor grammar ;-) --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
