Reviving this thread again: Our production appid now blows the 60s deadline and won't start new instances. The exact same code on our sandbox appid starts in under 20s.
We have instance(s) running and serving traffic so we're not down. But I can't get a new version warmed up, so I can't deploy new code. I've filed a production issue. Many attempts to start an instance fail. The "hot instance" theory certainly makes sense but does that mean my app is pinned to a hot instance? This seems like a bad idea. It seems to me that startup requests really need to be allowed more than 60s. The risk of a GAE slowdown producing user-facing downtime is high... and based on the (highly unscientific) poll in this thread, my normally-20s startup times are not atypical for a Java app. Jeff -- 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.
