Yes, I'll give a shot to profiling with Appstats, but it's looking a lot like an availability problem on the part of GAE. That error (203) I don't get it much, but the HTTP 500 is happening everyday for several URLs. Those URLs "normally" load within the 1000ms and very often in a lot less time, but apparently a cold start sometime takes more than 30000ms. The pages are not complex (and I am not using any tasks queue) and the queries to the datastore shouldn't take that time at all. I don't know after how many minutes the instance goes to "sleep", but I'm planning on using some cron jobs to keep it awake, at least until things stabilize.
For me a good indication that the system is not behaving as well as the GAE status page shows is the fact that I myself often get an Internal error on the Admin console just by trying to refresh the logs page. Right now the logs are behind at least an hour, which I never experienced before. On Dec 1, 3:04 pm, Erwin Streur <[email protected]> wrote: > As the message subtly indicated the problem is not in the execution of > your code handling the request, but the Google System preparing itself > for delegating the request to your code. > > Probably it is trying to startup a new instance, but fails to do so > within 10 seconds ( check the Request Time/Latency value). There can > be a number of causes for this ranging from general stress on the > Google system to too many libraries and/or too many lengthy static > initialisation of classes. -- 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.
