One of the proposed solutions here (and now officially on the roadmap - wooo!) is the ability to pay a fee to keep your JVM "warm" and reduce the currently-frequent occurrences of startup.
See http://groups.google.com/group/google-appengine-java/msg/dafc502f0957c58a for an overview of this and similar issues. On Mar 25, 5:29 pm, gholler <[email protected]> wrote: > When GAE is load balancing your app, and it decides to start up a new > instance, why are they sending a client request as the first hit to > your app? Unless your app is trivial, you're going to have some > startup time. It's not a good job of load balancing if requests are > sent to an instance that isn't even started yet. This is killing our > app. The load balancer should get an HTTP 200 back from our instance > before sending any real traffic that way. > > Am I off-base here? Is anyone else deploying an app with a rich client > and a datastore back-end where this isn't a problem? I couldn't find > anyone at the Server Side Java Symposium last week that was deploying > to GAE. > > G -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" 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-java?hl=en.
