Jeff, I believe that you had asked on this list, a while ago: In what circumstance is it _ever_ good for user requests to see cold starts?
Did you ever get an answer to that? That is the part that puzzles me still. Is it just too hard? Maybe they don't have a _scalable_ algorithm for directing requests to already-existing instances? Anyway, with all of the focus on the Compute Engine side, I wonder if improvements to App Engine are going to deprioritized. On Wednesday, May 15, 2013 4:52:51 PM UTC-7, Jeff Schnitzer wrote: > > I attended the "Autoscaling Java" session at Google I/O. In summary, the > advice is: > > * Don't use dependency injection. > * Don't use AOP. > * Hardcode configuration values as much as possible. > > In other words, go back to Java circa 2002. There was no discussion of > changing routing so that user requests don't see cold starts. I asked about > this in person - apparently they're still "talking about it" and nothing > has been done about it. > > I am sad. > > Jeff > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at http://groups.google.com/group/google-appengine?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
