Unfortunately, it isn't that high in terms of stars: https://code.google.com/p/googleappengine/issues/list
On Tuesday, 21 May 2013 10:35:10 UTC+1, Ian Marshall wrote: > > I am sure that most, if not all, contributors to this thread (except > perhaps Google's own Matt Stephenson!) have already starred GAE Issue > 7865 (User-facing requests should never be locked to cold instance > starts) at: > > > > https://code.google.com/p/googleappengine/issues/detail?id=7865&colspec=ID%20Type%20Component%20Status%20Stars%20Summary%20Language%20Priority%20Owner%20Log > > > It was raised, acknowledged and accepted last summer and has currently > got 155 stars. > > If there is a "Beg" panel for this issue, I shall visit it and click > the "Beg" icon. > > > On May 21, 10:11 am, Ian Marshall <ianmarshall...@gmail.com> wrote: > > If (even an experimental) switch labelled > > > > "Route requests to warmed-up instances only (except if none is > > already running)" > > > > was introduced, I think that you will find a huge take-up, which will > > indicate the strong desire/need of GAE/J developers for such a > > feature! > > > > On May 21, 8:54 am, Marcel Manz <marcel.m...@gmail.com> wrote: > > > > > > > > > > > > > > > > > Hi Matt, > > > > > Thanks for your feedback. > > > > > I really would like to unterstand the reason for Google being unable > to > > > introduce a switch labeled "route to warmed up instances only". > > > > > What is so complicated with that? > > > > > Personally I don't want API controls for min-idle/resident/scaling > > > instances, as it still doesn't guarantee that requests never get > routed to > > > cold starts. As a matter of fact that's exactly what has been observed > by > > > most: idling resident instances waiting longer for doing nothing, > while new > > > dynamic instances get hit with cold starts. Further, we're using PAAS > to > > > exactly not have to take care on controlling such scaling / cold start > > > issues. If I have to take care on it, then this would be the wrong > platform > > > for me. > > > > > To me I really don't care if the instances take one, two or more > seconds to > > > boot. It's unacceptable to *ever* have requests getting directed to > cold > > > starts. > > > > > Would Adwords run on this system, Google would be losing billions of > > > dollars, if viewers would be presented with ads 2 seconds, 1 second or > even > > > few hundred milliseconds too late. > > > > > We don't want that and all we're asking for is consistent performance > in > > > response times. That requires routing to warmed up instances only. > > > > > Can you please spend that 1 Million it might take your engineers to > adapt > > > the scheduler to the way it should be, as it will greatly pay you off > in > > > the long run.You really have to do this, if you want to become an > Amazon > > > killer and win the crowd for your platform. > > > > > Marcel > -- 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.
