This is very disturbing ... Our M/S app is getting higher error rates and some instances take from 15s to 70s to start. We can't do anything about this and even debug what is happening. If there was a issue with our code, they should always take 70s to start! I really can't understand or think about what in our code we are loading the whole world to take all that time... Then the solutions is: move to HRD and ... experience the same load time on app startup??? So, what can I do!!!
Sorry to the rude speaking but I'm very concerned. We started the process to get operational support and plan our migration to have the SLA, but if our app startup will continue taking a lot of time I really can imagine what to do... Googlers, does the startup problem is getting solved for both M/S and HRD? Only HRD? None? Is there any thing we can do to avoid that strange behavior of our instances? Instance startup seems to be vital to the application's health: if your app takes to much time to startup then all concurrent requests to that instances die with 500's. This is very odd, and the "warmup" requests seems to never work. By our observations and other people observations, even if you set a fixed min_idle instances to be always there, they don't serve the traffic and you still get errors! Hope to see some answers, we really liked GAE in our first year woking with the platform, and now I feel completely lost... Best Regards, -Ronoaldo Em terça-feira, 13 de março de 2012 07h51min03s UTC-3, Richard Watson escreveu: > > My graph showing ms/sec (attached) over last 24h. Average spikes were up > to 32 seconds, but I think all the errors were 60+-1 sec. > > On Tuesday, March 13, 2012 10:36:38 AM UTC+2, Richard Watson wrote: >> >> In case you're keeping track of issues thinking it's generally cleared up: >> >> I'm on HR and have noticed higher latencies (couple seconds instead of >> e.g. 300ms) lately and sometimes higher error rates (a few instead of 0-3). >> Yesterday over about 6 hours I got a ton of 60-second requests that threw >> 500's with accompanying messages [1], usually on memcache sets hitting a >> deadline exceeded. Also, over the last couple weeks I've been running 3 >> instances permanently despite sometimes shutting them down manually. >> Usually I get by on one just fine with bursts of 2 or 3. I've noticed >> that one instance serves the majority of traffic with the other two serving >> maybe 50 requests over many hours, so the shutdown isn't aggressive enough. >> >> "This request caused a new process to be started for your application..." >> + >> "A problem was encountered with the process that handled this request, >> causing it to exit" in the same request. >> >> App-id: 2dumo-hr >> > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/6r3NpHShJcgJ. 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.
