Just for the record we got hit again 11:00pm (3:00pm GMT+8) today.

I have nearly finished moving all of our data to a new instance, and
am just testing everything.
Then we will cut over to an instance that doesn't exhibit these
problems.

T

On Nov 30, 5:12 pm, Tim Hoffman <[email protected]> wrote:
> Hi
>
> For the last week I have been continually complaining about a high
> incidence of DeadlineExceededErrors hitting only one of two instances
> running the same code at exactly the same time each day.  I have yet
> to get any sort of response from google.
>
> As promised I have written up in more detail what we are experiencing,
> graphed response times over several dats, presented debugs logs and
> generally discussed what I believe is going on.
>
> The full document and supporting data can be viewed here,
>
> http://docs.google.com/Doc?docid=0Ad1LTa6ONStgZGYzcXhjeHBfMTIwZGs2NWd...
>
> It is clear to me that app engine instance performance (specifically
> startup times) can be heavily influenced by where your app has been
> deployed and what is going on inside google, and this can have more
> impact on how your applications perform than your own code.
>
> I hope have done enough to attract some attention from google staff
> and would really like to discuss with them their take on my findings
> and look at ways of resolving this issue.
>
> Regards
>
> Tim Hoffman

--

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.


Reply via email to