I don't have an answer for the auto scaling of backends, but maybe you could accomplish your task through a combination of Backends and Frontend instances.
You says that the reason you were having issues with frontend instance was because of high startup time caused by intense processing. Would it possible to move the processing to the backend, but still have the frontend instance handle requests? You could have the backend do the processing, then whenever you need to startup a new frontend instance you could have it request the precomputed values from the backend. Just a thought. - Kyle On Thursday, July 12, 2012 12:42:04 PM UTC-5, turbofrank wrote: > > Hi everyone, > > I've inherited an application built on GAE that has an abnormally high > startup time due to intense processing to fill a local cache. Standard GAE > instances were not working for us, so we had to move to backends. I have a > couple of questions: > > 1) If our traffic spikes to levels higher than the backend can handle, > does GAE do anything? I've noticed during higher traffic, our instance > being terminated often (_ah/stop). This means 10-20 minutes while a new > instance spins up, and our app is down. Anyone else experiencing this? > I'm guessing I will need to put up more backends. :( > > 2) Is there any way to configure auto scaling of backends so that I don't > have to pay for several instances just hanging around during low traffic > hours? > > Thank you, > Frank > > > > -- 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/-/JheijFxAy_4J. 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.
